pivotoolz 0.1.1

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: aa29aaa29d023de131d5d30f72546d8932426390
+  data.tar.gz: 68ef16bf42bab12f8db92d0a8d953dc5a7d20ded
+SHA512:
+  metadata.gz: 88beb076fadf9cf742cdc3f41d5f012e7e497358eb9302a629039e9cf51091637fb9a32ce790bdfb1aae8a152f45de4348659bc30e994930b89d85acba3082b6
+  data.tar.gz: 4b6ff5b8cc673dbee17244623038a0fe605064825172178ca057d249c2bbc94ea1fee3b015059207cdee1588c19b0a79d3a290457e81656bff8a73cf601033bb

data/.gitignore

@@ -0,0 +1,11 @@
+/.bundle/
+/.yardoc
+/_yardoc/
+/coverage/
+/doc/
+/pkg/
+/spec/reports/
+/tmp/
+
+# rspec failure tracking
+.rspec_status

data/.rspec

@@ -0,0 +1,3 @@
+--format documentation
+--color
+--require spec_helper

data/.travis.yml

@@ -0,0 +1,5 @@
+sudo: false
+language: ruby
+rvm:
+  - 2.4.1
+before_install: gem install bundler -v 1.16.1

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,74 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at pair+sufyanadam@gmail.com. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

data/Gemfile

@@ -0,0 +1,6 @@
+source "https://rubygems.org"
+
+git_source(:github) {|repo_name| "https://github.com/#{repo_name}" }
+
+# Specify your gem's dependencies in pivotoolz.gemspec
+gemspec

data/Gemfile.lock

@@ -0,0 +1,51 @@
+PATH
+  remote: .
+  specs:
+    pivotoolz (0.1.1)
+      rest-client (~> 2.0.2)
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    diff-lcs (1.3)
+    domain_name (0.5.20170404)
+      unf (>= 0.0.5, < 1.0.0)
+    http-cookie (1.0.3)
+      domain_name (~> 0.5)
+    mime-types (3.1)
+      mime-types-data (~> 3.2015)
+    mime-types-data (3.2016.0521)
+    netrc (0.11.0)
+    rake (10.4.2)
+    rest-client (2.0.2)
+      http-cookie (>= 1.0.2, < 2.0)
+      mime-types (>= 1.16, < 4.0)
+      netrc (~> 0.8)
+    rspec (3.6.0)
+      rspec-core (~> 3.6.0)
+      rspec-expectations (~> 3.6.0)
+      rspec-mocks (~> 3.6.0)
+    rspec-core (3.6.0)
+      rspec-support (~> 3.6.0)
+    rspec-expectations (3.6.0)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.6.0)
+    rspec-mocks (3.6.0)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.6.0)
+    rspec-support (3.6.0)
+    unf (0.1.4)
+      unf_ext
+    unf_ext (0.0.7.4)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  bundler (~> 1.16)
+  pivotoolz!
+  rake (~> 10.0)
+  rspec (~> 3.0)
+
+BUNDLED WITH
+   1.16.1

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2018 Sufyan Adam
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/README.md

@@ -0,0 +1,144 @@
+# Pivotoolz
+
+Ever forget to deliver a story while waiting for your continuous
+deployment build to go green and deployment to finish? Never let
+another story slip through the cracks into production again with
+Pivotoolz! Ever wish stories would deliver themselves on successful
+deployment? This gem is for you!
+
+Pivotoolz is a set of tools to automate your development process when
+using Pivotal Tracker for managing your backlog. Save yourself time
+and increase your productivity. Use the tools individually or compose
+them together to automate anything related to pivotal tracker stories.
+
+## Installation
+
+Add this line to your application's Gemfile:
+
+```ruby
+gem 'pivotoolz'
+```
+
+And then execute:
+
+    $ bundle
+
+Or install it yourself as:
+
+    $ gem install pivotoolz
+
+## Usage
+
+Pivotoolz is a collection of tiny programs that can be used individually
+or composed together for more powerful features. The manner of usage of
+each is described below:
+
+### `deliver-deployed-stories`
+
+Deliver all stories that have been deployed to the given
+environment since the previous and last deployment.
+
+Example:
+`bundle exec deliver-deployed-stories ENVIRONMENT`
+
+Where `ENVIRONMENT` is the environment you consider to be where stories
+can be accepted/rejected.
+
+Example:
+Let's say we have an `acceptance` environment where we deploy our app to
+test out stories. As long as we label our deployed git SHAs with tags
+(using `tag-it`), we can automatically deliver any finished stories
+that went out in the last deployment by simply running the command:
+
+`bundle exec deliver-deployed-stories acceptance`
+
+### `deliver-story`
+
+Deliver a given story provided in JSON format. The minimum JSON attributes
+required are `id` and `current_state`
+
+Typically used with output from `get-story-info-from-id` piped in.
+
+Example:
+`bundle exec get-story-info-from-id STORY_ID | bundle exec deliver-story`
+  OR
+`bundle exec deliver-story '{"id": 123, "current_state": "finished"}'`
+
+If `current_state` is not `finished`, the story will not be delivered.
+
+### `stories-deployed`
+
+Returns a list of all stories deployed to a given environment.
+
+Output is of the form:
+
+STORY_TITLE:
+LINK_TO_STORY
+
+STORY_TITLE:
+LINK_TO_STORY
+
+Example:
+```
+bundle exec stories-deployed production
+# Output:
+
+Update README:
+https://www.pivotaltracker.com/story/show/123
+
+Update dependencies
+https://www.pivotaltracker.com/story/show/456
+
+```
+
+Use with `post-slack-message` to post a message in a slack deployment channel
+with the list of stories that just got deployed.
+
+### `post-slack-message`
+
+Post a message to a slack channel. You will need to [setup
+a webhook integration](https://api.slack.com/incoming-webhooks) on slack first.
+Once you have done so, copy your Webhook URL into
+an environment variable `SLACK_WEBHOOK_URL`.
+If the `SLACK_WEBHOOK_URL` has been defined correctly, you will
+be able to post a message in slack to any channel as follows:
+`bundle exec post-slack-message CHANNEL "MESSAGE_TEXT"`
+Where CHANNEL is of the form "#channel" or "@user".
+
+You can also pipe a message to the `post-slack-message` program. For
+example:
+`{ echo Stories deployed to production:; bundle exec stories-deployed production; } | bundle exec post-slack-message '#production-deploys'`
+
+### `story-ids-deployed`
+
+Returns a newline delimited list of all story ids deployed
+to the given environment.
+
+Example:
+```
+bundle exec story-ids-deployed production
+
+# Output:
+123
+456
+
+```
+
+
+## Development
+
+After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
+
+To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org).
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at https://github.com/sufyanadam/pivotoolz. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
+
+## License
+
+The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
+
+## Code of Conduct
+
+Everyone interacting in the Pivotoolz project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/sufyanadam/pivotoolz/blob/master/CODE_OF_CONDUCT.md).

data/Rakefile

@@ -0,0 +1,6 @@
+require "bundler/gem_tasks"
+require "rspec/core/rake_task"
+
+RSpec::Core::RakeTask.new(:spec)
+
+task :default => :spec

data/bin/console

@@ -0,0 +1,14 @@
+#!/usr/bin/env ruby
+
+require "bundler/setup"
+require "pivotoolz"
+
+# You can add fixtures and/or initialization code here to make experimenting
+# with your gem easier. You can also use a different console, if you like.
+
+# (If you use this, don't forget to add pry to your Gemfile!)
+# require "pry"
+# Pry.start
+
+require "irb"
+IRB.start(__FILE__)

data/bin/setup

@@ -0,0 +1,8 @@
+#!/usr/bin/env bash
+set -euo pipefail
+IFS=$'\n\t'
+set -vx
+
+bundle install
+
+# Do any other automated setup that you need to do here

data/exe/deliver-deployed-stories

@@ -0,0 +1,10 @@
+#!/usr/bin/env ruby
+
+environment_tag = ARGV[0]&.strip
+
+if environment_tag.nil? || environment_tag.empty?
+  puts "Usage: deliver-deployed-stories ENVIRONMENT"
+  exit 1
+end
+
+puts `story-ids-deployed #{environment_tag} | get-story-info-from-id | deliver-story`

data/exe/deliver-story

@@ -0,0 +1,36 @@
+#!/usr/bin/env ruby
+
+require('json')
+require('ostruct')
+require('rest-client')
+
+stream = ARGV.any? ? ARGV : ARGF
+if stream == ARGF && $stdin.tty?
+  puts "Usage: deliver-story STORY_INFO_JSON"
+  puts "Examples:\n deliver-story  '{\"id\":123,\"current_state\":\"started\"}'"
+  puts %Q[ echo '{"id":123,"current_state":"started"}' | deliver-story]
+  exit 1
+end
+
+stream.each do |story_hash|
+  story = OpenStruct.new(JSON.parse(story_hash))
+  story_state = story.current_state
+  if story_state != 'finished'
+    puts "Story #{story.id} is not finished, not delivering"
+    next
+  end
+
+  story_url = "https://www.pivotaltracker.com/services/v5/stories/#{story.id}"
+  begin
+    response = RestClient::Request.execute(
+      method: :put,
+      url: story_url,
+      payload: {current_state: 'delivered'},
+      headers: {'X-TrackerToken' => ENV['PIVOTAL_TRACKER_API_TOKEN']}
+    )
+
+    puts response
+  rescue RestClient::Exception => e
+    puts "Error delivering story #{story.id}, #{e.message}:\n#{e.backtrace.join("\n")}"
+  end
+end

data/exe/get-story-info-from-id

@@ -0,0 +1,30 @@
+#!/usr/bin/env ruby
+
+require 'open-uri'
+require 'json'
+
+def get_story_info(story_id)
+  return nil if story_id.empty?
+
+  begin
+    open("https://www.pivotaltracker.com/services/v5/stories/#{story_id}", 'X-TrackerToken' => ENV['PIVOTAL_TRACKER_API_TOKEN']).read
+  rescue StandardError => e
+    JSON.generate({error: "could not get story info for story #{story_id}: #{e.message}\nstory info may be available at https://www.pivotaltracker.com/story/show/#{story_id}"})
+  end
+end
+
+stream = ARGV.any? ? ARGV : ARGF
+
+if stream == ARGF && $stdin.tty?
+  puts "Usage:\nget-story-info-from-id STORY_ID\n"
+  puts " OR\n"
+  puts "echo STORY_ID | get-story-info-from-id"
+  exit 1
+end
+
+infos = stream.reduce([]) do |reduced, story_id|
+  next reduced unless story_id && story_id =~ /\d+/
+  reduced << get_story_info(story_id.strip)
+end
+
+puts infos.join("\n")

data/exe/merge

@@ -0,0 +1,29 @@
+#!/usr/bin/env ruby
+
+target_branch = ARGV[0]&.strip
+
+if target_branch.nil? || target_branch.empty?
+  puts "You must provide a target branch name!"
+  exit 1
+end
+
+current_branch  = `git rev-parse --abbrev-ref HEAD`.strip
+branch_to_merge = current_branch
+
+puts "Running git pull origin #{current_branch} --rebase\n\n"
+
+`git checkout #{target_branch}`
+`git pull origin #{target_branch} --rebase`
+
+puts "\nRebasing #{target_branch} into #{branch_to_merge}\n\n"
+`git checkout #{branch_to_merge}`
+`git rebase #{target_branch}`
+
+puts "\nForce pushing #{branch_to_merge}\n\n"
+`git push origin #{branch_to_merge} -f`
+
+puts "\nCompleting the merge of #{branch_to_merge} into #{target_branch}\n\n"
+`git checkout #{target_branch}`
+`git merge #{branch_to_merge} --no-ff --no-edit`
+
+puts "\nMerge complete, you must run git push origin #{target_branch} manually to complete the merge\n"

data/exe/post-slack-message

@@ -0,0 +1,24 @@
+#!/usr/bin/env ruby
+
+require 'rest-client'
+require 'json'
+
+URL = ENV['SLACK_WEBHOOK_URL']
+
+channel = ARGV.shift
+content = ARGV.empty? ? ARGF.read : StringIO.new(ARGV.join("\n")).read
+exit 0 if content.empty?
+
+begin
+  RestClient.post(
+    URL,
+    payload: {
+      username: ENV['SLACKBOT_USERNAME'] || 'slackbot',
+      channel: channel,
+      text: content,
+      icon_emoji: ":ghost:"
+    }.to_json
+  )
+rescue RestClient::Exceptions => e
+  puts "Error posting to slack #{e.message}:\n#{e.backtrace}"
+end

data/exe/stories-deployed

@@ -0,0 +1,22 @@
+#!/usr/bin/env ruby
+
+require 'json'
+require 'ostruct'
+
+environment_tag = ARGV[0]&.strip
+
+if environment_tag.nil? || environment_tag.empty?
+  puts "Usage: stories-deployed ENVIRONMENT"
+  exit 1
+end
+
+deployed_story_infos = `story-ids-deployed #{environment_tag} | get-story-info-from-id`
+
+stories_deployed = deployed_story_infos.split("\n").compact.reduce([]) do |reduced, story_info|
+  story = OpenStruct.new(JSON.parse(story_info))
+
+  reduced << "#{story.error}"
+  reduced << "#{story.name}:\n#{story.url}"
+end
+
+puts stories_deployed

data/exe/story-ids-deployed

@@ -0,0 +1,24 @@
+#!/usr/bin/env ruby
+
+environment_tag = ARGV[0]&.strip
+
+if environment_tag.nil? || environment_tag.empty?
+  puts "Usage: story-ids-deployed ENVIRONMENT"
+  exit 1
+end
+
+commit_range = `git tag -l #{environment_tag}* | tail -n 2 | tr '\n' ' ' | sed -e 's/ /../'`
+
+if commit_range.nil? || commit_range.empty?
+  puts "Empty commit range! Are there any commits tagged with #{environment_tag}?"
+  exit 1
+end
+
+commit_message_bodies = `git log --pretty=%b #{commit_range}`.strip
+story_ids = commit_message_bodies.
+  scan(/\[Finishes\s*#(\d+)|,\s*#(\d+)\]|Fixes\s*#(\d+)|,\s*#(\d+)|#(\d+)\]/).
+  flatten.
+  compact.
+  uniq
+
+puts story_ids.join("\n")

data/exe/tag-it

@@ -0,0 +1,17 @@
+#!/usr/bin/env ruby
+
+tag = ARGV[0]
+
+if tag
+  timestamp = `date -u +'%Y%m%d%H%M%S'`
+  full_tag = "#{tag}/#{timestamp}"
+  tag_exists = `git log HEAD --no-walk -1 --pretty='%h%d'`.include? "tag: #{tag}"
+
+  if tag_exists
+    puts "Already tagged #{tag}!"
+    exit 0
+  end
+
+  `git tag #{full_tag}`
+  `git push origin #{full_tag}`
+end

data/lib/pivotoolz.rb

@@ -0,0 +1,5 @@
+require "pivotoolz/version"
+
+module Pivotoolz
+  # Your code goes here...
+end

data/lib/pivotoolz/version.rb

@@ -0,0 +1,3 @@
+module Pivotoolz
+  VERSION = "0.1.1"
+end

data/pivotoolz.gemspec

@@ -0,0 +1,38 @@
+
+lib = File.expand_path("../lib", __FILE__)
+$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
+require "pivotoolz/version"
+
+Gem::Specification.new do |spec|
+  spec.name          = "pivotoolz"
+  spec.version       = Pivotoolz::VERSION
+  spec.authors       = ["Sufyan Adam"]
+  spec.email         = ["sufyan@sealmail.net"]
+
+  spec.summary       = %q{Tools to save you time when working with Pivotal Tracker stories}
+  spec.description   = %q{Auto-deliver your finished stories upon successful deployment, find out which stories went out in the last deployment}
+  spec.homepage      = "https://github.com/sufyanadam/pivotoolz"
+  spec.license       = "MIT"
+
+  # Prevent pushing this gem to RubyGems.org. To allow pushes either set the 'allowed_push_host'
+  # to allow pushing to a single host or delete this section to allow pushing to any host.
+  if spec.respond_to?(:metadata)
+    spec.metadata["allowed_push_host"] = "https://rubygems.org"
+  else
+    raise "RubyGems 2.0 or newer is required to protect against " \
+      "public gem pushes."
+  end
+
+  spec.files         = `git ls-files -z`.split("\x0").reject do |f|
+    f.match(%r{^(test|spec|features)/})
+  end
+  spec.bindir        = "exe"
+  spec.executables   = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }
+  spec.require_paths = ["lib"]
+
+  spec.add_dependency 'rest-client', "~> 2.0.2"
+
+  spec.add_development_dependency "bundler", "~> 1.16"
+  spec.add_development_dependency "rake", "~> 10.0"
+  spec.add_development_dependency "rspec", "~> 3.0"
+end

metadata

@@ -0,0 +1,132 @@
+--- !ruby/object:Gem::Specification
+name: pivotoolz
+version: !ruby/object:Gem::Version
+  version: 0.1.1
+platform: ruby
+authors:
+- Sufyan Adam
+autorequire: 
+bindir: exe
+cert_chain: []
+date: 2018-03-05 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: rest-client
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 2.0.2
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 2.0.2
+- !ruby/object:Gem::Dependency
+  name: bundler
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.16'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.16'
+- !ruby/object:Gem::Dependency
+  name: rake
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '10.0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '10.0'
+- !ruby/object:Gem::Dependency
+  name: rspec
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '3.0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '3.0'
+description: Auto-deliver your finished stories upon successful deployment, find out
+  which stories went out in the last deployment
+email:
+- sufyan@sealmail.net
+executables:
+- deliver-deployed-stories
+- deliver-story
+- get-story-info-from-id
+- merge
+- post-slack-message
+- stories-deployed
+- story-ids-deployed
+- tag-it
+extensions: []
+extra_rdoc_files: []
+files:
+- ".gitignore"
+- ".rspec"
+- ".travis.yml"
+- CODE_OF_CONDUCT.md
+- Gemfile
+- Gemfile.lock
+- LICENSE.txt
+- README.md
+- Rakefile
+- bin/console
+- bin/setup
+- exe/deliver-deployed-stories
+- exe/deliver-story
+- exe/get-story-info-from-id
+- exe/merge
+- exe/post-slack-message
+- exe/stories-deployed
+- exe/story-ids-deployed
+- exe/tag-it
+- lib/pivotoolz.rb
+- lib/pivotoolz/version.rb
+- pivotoolz.gemspec
+homepage: https://github.com/sufyanadam/pivotoolz
+licenses:
+- MIT
+metadata:
+  allowed_push_host: https://rubygems.org
+post_install_message: 
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+required_rubygems_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements: []
+rubyforge_project: 
+rubygems_version: 2.6.11
+signing_key: 
+specification_version: 4
+summary: Tools to save you time when working with Pivotal Tracker stories
+test_files: []