git_flower 0.1.1

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 437cd16229bd94b676971ac50d6b86f4d792fe64
+  data.tar.gz: 171eee617b2500ead9a364c380effc833e1e082a
+SHA512:
+  metadata.gz: ab3da35e297f3cab5bda3d0056722712f3dd659726139b43a6c5f3dbca42b5e98837e2b142eb43c92a99cbde882f3250a7eb0daa30f7f06ba11d84153c2a0e0c
+  data.tar.gz: 26397d79ff5f5deb4157587c1cab10c798271d65c6dbfa8e2c1dc24383370525712bfd65f372face2021b6d292d8ae5b1feb1f910312f4cd34c2acc9d3a4a936

data/.gitignore

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

data/.rspec

@@ -0,0 +1,2 @@
+--format documentation
+--color

data/.travis.yml

@@ -0,0 +1,5 @@
+sudo: false
+language: ruby
+rvm:
+  - 2.4.1
+before_install: gem install bundler -v 1.15.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 alex.wilkinson@me.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,4 @@
+source "https://rubygems.org"
+
+# Specify your gem's dependencies in git_flower.gemspec
+gemspec

data/Gemfile.lock

@@ -0,0 +1,89 @@
+PATH
+  remote: .
+  specs:
+    git_flower (0.1.1)
+      activesupport (~> 5.1.2)
+      faraday (~> 0.9.0)
+      git (~> 1.3.0)
+      thor (~> 0.19.4)
+      tracker_api (= 0.2.9)
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    activemodel (5.1.2)
+      activesupport (= 5.1.2)
+    activesupport (5.1.2)
+      concurrent-ruby (~> 1.0, >= 1.0.2)
+      i18n (~> 0.7)
+      minitest (~> 5.1)
+      tzinfo (~> 1.1)
+    addressable (2.5.1)
+      public_suffix (~> 2.0, >= 2.0.2)
+    axiom-types (0.1.1)
+      descendants_tracker (~> 0.0.4)
+      ice_nine (~> 0.11.0)
+      thread_safe (~> 0.3, >= 0.3.1)
+    byebug (9.0.6)
+    coercible (1.0.0)
+      descendants_tracker (~> 0.0.1)
+    concurrent-ruby (1.0.5)
+    descendants_tracker (0.0.4)
+      thread_safe (~> 0.3, >= 0.3.1)
+    diff-lcs (1.3)
+    equalizer (0.0.11)
+    excon (0.57.1)
+    faraday (0.9.2)
+      multipart-post (>= 1.2, < 3)
+    faraday_middleware (0.11.0.1)
+      faraday (>= 0.7.4, < 1.0)
+    git (1.3.0)
+    i18n (0.8.5)
+    ice_nine (0.11.2)
+    minitest (5.10.2)
+    multipart-post (2.0.0)
+    public_suffix (2.0.5)
+    rake (10.5.0)
+    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)
+    thor (0.19.4)
+    thread_safe (0.3.6)
+    tracker_api (0.2.9)
+      activemodel
+      activesupport
+      addressable
+      excon
+      faraday (~> 0.9.0)
+      faraday_middleware
+      virtus
+    tzinfo (1.2.3)
+      thread_safe (~> 0.1)
+    virtus (1.0.5)
+      axiom-types (~> 0.1)
+      coercible (~> 1.0)
+      descendants_tracker (~> 0.0, >= 0.0.3)
+      equalizer (~> 0.0, >= 0.0.9)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  bundler (~> 1.15)
+  byebug
+  git_flower!
+  rake (~> 10.0)
+  rspec (~> 3.0)
+
+BUNDLED WITH
+   1.15.1

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2017 Alex Wilkinson
+
+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,115 @@
+# GitFlower
+
+GitFlower is a command-line utility that starts features and hotfixes using the git-flow branching model and creates corresponding features and bugs on PivotalTracker using the Pivotal API. Link tickets in Pivotal with your git-flow branches without leaving the comfort of the command line!
+
+While GitFlower only supports Pivotal at the moment, the plan is to add support for all popular project management systems. Once I have developed an adapter system for easily working with multiple APIs, I will publish my priority list on this README.
+
+If I'm not currently planning on adding your favorite PM tool, or it's not happening fast enough, feel free to contribute!
+
+## Installation
+
+Add this line to your application's Gemfile:
+
+```ruby
+gem 'git_flower'
+```
+
+And then execute:
+
+    $ bundle
+
+Or install it yourself as:
+
+    $ gem install git_flower
+
+You will have to export your Pivotal API Key and a Project ID from your
+environment. Here's an example of how to do so in ZSH:
+
+```zsh
+export PIVOTAL_TOKEN="TOKEN HERE"
+export PIVOTAL_PROJECT_ID="some_number_here"
+```
+
+## Usage
+
+The `git-flower create` commands will create a Pivotal story for your feature or hotfix, start a git-flow branch off of develop, and check out that branch. All you need to do is pass a story name, and it will set a titleized version as the Pivotal ticket name and a slugified version as the branch name.
+
+The commands won't run under the following conditions:
+
+  * You have added but uncommitted git changes.
+  * Local develop is not up to date with origin.
+
+By default, it will use `$USER` as the owner of the Pivotal story. For Pivotal to properly assign the owner, the name of your Pivotal user needs to match`$USER`.
+
+### Feature
+
+To create a new feature, with optional labels for the Pivotal feature, run the
+following:
+
+    $ git-flower feature create [NAME] [--labels=one two three]
+
+So if you wanted to create a Pivotal feature named "Save All The Cats" with the labels `cat` and `life-goal`, you could execute the following:
+
+    $ git-flower feature create "Save All The Cats" --labels cat life-goal
+
+And you will be checked out to the following branch, where the number
+represents the Pivotal Story ID.
+
+```
+feature/1234-save-all-the-cats
+```
+
+Your Pivotal Feature would look something like this:
+
+![Pivotal Feature Example](https://photos-1.dropbox.com/t/2/AADrhIDYH53IfCbz1VtLnPrNYX0MIHau-ub8g2cqxyclxQ/12/49046/png/32x32/3/1499760000/0/2/git-flower-feature.png/EIbdIhi4-dHgBCACKAI/-z2SbCaiHwKR-cyBs3xEw6ru8kdKgh7Fr8NEtw75NFI?dl=0&size=2048x1536&size_mode=3)
+
+### Hotfix
+
+To create a new hotfix, with optional labels for the Pivotal bug, run the
+following:
+
+    $ git-flower hotfix create [NAME] [--labels=one two three]
+
+So if you wanted to create a Pivotal bug named "Missing Cat" with
+the labels `cat` and `nightmare`, you could execute the following:
+
+    $ git-flower hotfix create "Missing Cat" --labels cat nightmare
+
+And you will be checked out to the following branch, where the number
+represents the Pivotal Story ID.
+
+```
+hotfix/5678-missing-cat
+```
+
+Your Pivotal Bug would look something like this:
+
+![Pivotal Bug Example](https://photos-2.dropbox.com/t/2/AADERZmXtrsHQ202P285d5je1vTwaRHK6PZtQTNkknzbjQ/12/49046/png/32x32/3/1499763600/0/2/git-flower-bug.png/EIbdIhi4-dHgBCACKAI/VCWQS444mMy3075Fb1w4mf4vmfuz5js8GPKfI87yI_M?dl=0&size=2048x1536&size_mode=3)
+
+### Hitch Integration
+
+If you're a pair programmer, and would like to set joint assignees on your
+Pivotal tickets using [Hitch](https://github.com/therubymug/hitch), make sure you have the library configured and have a `.hitchrc` file in your home directory.
+
+If all is set up correctly, GitFlower will detect who you are hitched with and
+add both as story owners. If you are not hitched with anyone, it will default
+to `$USER`.
+
+## 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 GitLab at https://gitlab.com/alexwilkinson/git-flower. 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](http://opensource.org/licenses/MIT).
+
+## Code of Conduct
+
+Everyone interacting in the GitFlower project’s code base and issue trackers is expected to follow the [code of conduct](https://gitlab.com/alexwilkinson/git-flower/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 "git_flower"
+
+# 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/git-flower

@@ -0,0 +1,4 @@
+#!/usr/bin/env ruby
+require_relative '../lib/git_flower/cli'
+
+GitFlower::CLI.start(ARGV)

data/git_flower.gemspec

@@ -0,0 +1,34 @@
+# coding: utf-8
+lib = File.expand_path("../lib", __FILE__)
+$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
+require "git_flower/version"
+
+Gem::Specification.new do |spec|
+  spec.name          = "git_flower"
+  spec.version       = GitFlower::VERSION
+  spec.authors       = ["Alex Wilkinson"]
+  spec.email         = ["alex.wilkinson@me.com"]
+
+  spec.summary       = %q{A CLI for starting git-flow features and hotfixes on PivotalTracker.}
+  spec.description   = %q{This library starts features and hotfixes using the git-flow branching model and creates corresponding features and bugs on PivotalTracker using the Pivotal API.}
+  spec.homepage      = "https://gitlab.com/alexwilkinson/git-flower"
+  spec.license       = "MIT"
+
+  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_development_dependency "bundler", "~> 1.15"
+  spec.add_development_dependency "rake", "~> 10.0"
+  spec.add_development_dependency "rspec", "~> 3.0"
+  spec.add_development_dependency "byebug"
+
+  spec.add_dependency "git", "~> 1.3.0"
+  spec.add_dependency "thor", "~> 0.19.4"
+  spec.add_dependency "activesupport", "~> 5.1.2"
+  spec.add_dependency "faraday", "~> 0.9.0"
+  spec.add_dependency "tracker_api", "0.2.9"
+end

data/lib/git_flower.rb

@@ -0,0 +1,9 @@
+require "git_flower/version"
+require "git_flower/story"
+require "git_flower/feature"
+require "git_flower/hotfix"
+require "git_flower/git_repository"
+require "git_flower/pivotal_project"
+
+module GitFlower
+end

data/lib/git_flower/cli.rb

@@ -0,0 +1,13 @@
+require 'thor'
+require_relative './feature-cli.rb'
+require_relative './hotfix-cli.rb'
+
+module GitFlower
+  class CLI < Thor
+    desc "feature SUBCOMMAND ...ARGS", "manage git-flow features"
+    subcommand "feature", GitFlower::FeatureCLI
+
+    desc "hotfix SUBCOMMAND ...ARGS", "manage git-flow hotfixes"
+    subcommand "hotfix", GitFlower::HotfixCLI
+  end
+end

data/lib/git_flower/feature-cli.rb

@@ -0,0 +1,58 @@
+require 'thor'
+require_relative 'feature'
+
+module GitFlower
+  class FeatureCLI < Thor
+    namespace :feature
+
+    desc "create STORY_NAME [--labels=one two three]", "Create hotfix story and git branch for it"
+    long_desc <<-desc
+      This script will create a feature pivotal story and start a feature branch for
+      you. All you need to do is pass a story name. It will then create the branch
+      name using a slugified version of the name you passed it.
+
+      It will detect who you are hitched with and add both as story owners.
+
+      It won't run under the following conditions:
+      \x5  * You have added but uncommitted git changes.
+      \x5  * If local develop is not up to date with origin.
+
+      If you want to use it, you have to add your Pivotal API Key and Pivotal
+      Project ID as environment variables.
+
+      You can find the your token at the bottom of the User Profile page on Pivotal,
+      which you can get to by clicking your name in the top right corner.
+      \x5  export PIVOTAL_TOKEN="TOKEN HERE"
+      \x5  export PIVOTAL_PROJECT_ID="some_number_here"
+
+      This script can also detect if you are "hitched" with someone using the
+      hitch gem (it reads ~/.hitchrc), and add who you are hitched with as story
+      owners.  If you don't hitch the Pivotal card will be assigned to $USER (note
+      your Pivotal user needs to match your unix user in this case)
+
+      > feature create 'Do The Needful'
+    desc
+
+    option :labels, type: :array, desc: "The labels you want to apply to your story"
+
+    def create(story_name)
+      feature = Feature.new(
+        story_name: story_name,
+        labels: options[:labels],
+        project_id: project_id,
+        pivotal_token: pivotal_token
+      )
+      feature.save!
+    end
+
+    private
+
+    def project_id
+      ENV['PIVOTAL_PROJECT_ID']
+    end
+
+    def pivotal_token
+      ENV['PIVOTAL_TOKEN']
+    end
+  end
+end

data/lib/git_flower/feature.rb

@@ -0,0 +1,23 @@
+require 'active_support/inflector'
+require_relative 'story'
+
+module GitFlower
+  class Feature < Story
+    def save!
+      validate_environment_and_arguments!
+      validate_git_repository!
+
+      create_feature!
+    end
+
+    private
+
+    def validate_git_repository!
+      GitRepository.new(Dir.pwd).validate_for_feature!
+    end
+
+    def create_feature!
+      create_story!("feature")
+    end
+  end
+end

data/lib/git_flower/git_repository.rb

@@ -0,0 +1,80 @@
+require 'git'
+
+class GitError < StandardError; end
+class GitFlowError < StandardError; end
+
+module GitFlower
+  class GitRepository
+    def initialize(path_to_repo)
+      @repo = find_git_repo(path_to_repo)
+    end
+
+    def validate_for_hotfix!
+      puts "Checking for commited files"
+      if has_added_files?
+        raise GitError, "Please commit or stash all added files."
+      end
+
+      puts "Checking if master and develop are up to date"
+      if !master_up_to_date? || !develop_up_to_date?
+        raise GitError, "Please pull --rebase master and develop"
+      end
+
+      puts "Checking for existing hotfix branch"
+      if has_existing_branch_name?("hotfix")
+        raise GitFlowError, "You already have an existing hotfix branch"
+      end
+    end
+
+    def validate_for_feature!
+      puts "Checking for commited files"
+      if has_added_files?
+        raise GitError, "Please commit or stash all added files."
+      end
+
+      puts "Checking if develop is up to date"
+      if !develop_up_to_date?
+        raise GitError, "Please pull --rebase develop"
+      end
+    end
+
+    private
+
+    def has_added_files?
+      !@repo.status.added.empty?
+    end
+
+    def master_up_to_date?
+      branch_up_to_date?('master')
+    end
+
+    def develop_up_to_date?
+      branch_up_to_date?('develop')
+    end
+
+    def has_existing_branch_name?(branch_name)
+      !@repo.branches.local.map(&:name).select { |name| name =~ /^#{branch_name}.*/ }.empty?
+    end
+
+    def branch_up_to_date?(branch_name)
+      @repo.revparse(branch_name) == @repo.revparse("origin/#{branch_name}")
+    end
+
+    def no_git_repo_can_be_found
+      !system 'git status'
+    end
+
+    def find_git_repo(initial_dir)
+      if no_git_repo_can_be_found
+        raise GitError
+      end
+
+      if Dir.exist?('.git')
+        Git.open(initial_dir)
+      else
+        Dir.chdir('..')
+        find_git_repo(Dir.pwd)
+      end
+    end
+  end
+end

data/lib/git_flower/hotfix-cli.rb

@@ -0,0 +1,58 @@
+require 'thor'
+require_relative 'hotfix'
+
+module GitFlower
+  class HotfixCLI < Thor
+    namespace :hotfix
+
+    desc "create STORY_NAME [labels]", "Create hotfix story and git branch for it"
+    long_desc <<-eoht
+      This script will create a bug pivotal story and start a hotfix branch for
+      you. All you need to do is pass a story name. It will then create the branch
+      name using a slugified version of the name you passed it.
+
+      It won't run under the following conditions:
+      \x5  * You have added but uncommitted git changes.
+      \x5  * If local master and develop are not up to date with origin.
+      \x5  * If you already have a local hotfix branch (because git-flow won't run)
+
+      If you want to use it, you have to add your Pivotal API Key and Pivotal
+      Project ID as environment variables.
+
+      You can find the your token at the bottom of the User Profile page on Pivotal,
+      which you can get to by clicking your name in the top right corner.
+      \x5  export PIVOTAL_TOKEN="TOKEN HERE"
+      \x5  export PIVOTAL_PROJECT_ID="some_number_here"
+
+      This script can also detect if you are "hitched" with someone using the
+      hitch gem (it reads ~/.hitchrc), and add who you are hitched with as story owners.
+      If you don't hitch the Pivotal card will
+      be assigned to $USER (note your Pivotal user needs to match your unix user
+      in this case)
+
+          create-hotfix create 'Do The Needful'
+    eoht
+
+    option :labels, type: :array, desc: "The labels you want to apply to your story"
+
+    def create(story_name)
+      hotfix = Hotfix.new(
+        story_name: story_name,
+        labels: options[:labels],
+        project_id: project_id,
+        pivotal_token: pivotal_token
+      )
+      hotfix.save!
+    end
+
+    private
+
+    def project_id
+      ENV['PIVOTAL_PROJECT_ID']
+    end
+
+    def pivotal_token
+      ENV['PIVOTAL_TOKEN']
+    end
+  end
+end

data/lib/git_flower/hotfix.rb

@@ -0,0 +1,23 @@
+require 'active_support/inflector'
+require_relative 'story'
+
+module GitFlower
+  class Hotfix < Story
+    def save!
+      validate_environment_and_arguments!
+      validate_git_repository!
+
+      create_hotfix!
+    end
+
+    private
+
+    def validate_git_repository!
+      GitRepository.new(Dir.pwd).validate_for_hotfix!
+    end
+
+    def create_hotfix!
+      create_story!("hotfix")
+    end
+  end
+end

data/lib/git_flower/pivotal_project.rb

@@ -0,0 +1,48 @@
+require 'tracker_api'
+
+module GitFlower
+  class PivotalProject
+    def initialize(pivotal_token, project_id)
+      client = TrackerApi::Client.new(token: pivotal_token)
+      # we only have one project so this works well
+      @project = client.project(project_id)
+    end
+
+    def create_story(type, options)
+      if type == "feature"
+        create_feature(options)
+      elsif type == "hotfix"
+        create_hotfix(options)
+      end
+    end
+
+    def create_hotfix(options)
+      story_owner_ids = find_users(options[:owner_usernames]).map(&:id)
+      project.create_story(name: options[:name],
+                           labels: options[:labels],
+                           story_type: 'bug',
+                           current_state: 'started',
+                           owner_ids: story_owner_ids)
+    end
+
+    def create_feature(options)
+      story_owner_ids = find_users(options[:owner_usernames]).map(&:id)
+      project.create_story(name: options[:name],
+                           labels: options[:labels],
+                           story_type: 'feature',
+                           current_state: 'started',
+                           estimate: 0,
+                           owner_ids: story_owner_ids)
+    end
+
+    private
+
+    attr_reader :project
+
+    def find_users(owner_usernames)
+      project.memberships.map(&:person).select do |person|
+        owner_usernames.include? person.email.split("@").first
+      end
+    end
+  end
+end

data/lib/git_flower/story.rb

@@ -0,0 +1,75 @@
+require 'shellwords'
+require 'yaml'
+require 'active_support'
+require_relative 'git_repository'
+require_relative 'pivotal_project'
+
+module GitFlower
+  class Story
+    def initialize(story_name:, labels:, project_id:, pivotal_token:)
+      @story_name = story_name
+      @labels = Array(labels)
+      @project_id = project_id
+      @pivotal_token = pivotal_token
+    end
+
+    def create_story!(type)
+      if type.nil? || !["feature", "hotfix"].include?(type)
+        raise ArgumentError, "You need to specify that your story is a feature or a hotfix"
+      end
+
+      story = pivotal_project.create_story(type,
+                                           name: story_name.titleize,
+                                           labels: labels,
+                                           owner_usernames: derive_story_owners)
+
+      puts "Your pivotal story is https://www.pivotaltracker.com/story/show/#{story.id}"
+      puts "Creating #{type} branch for #{story_name}"
+
+      `git flow #{type} start #{branch_name(story.id)}`
+    end
+
+    private
+
+    attr_reader :story_name, :labels, :project_id, :pivotal_token
+
+    def validate_environment_and_arguments!
+      if env_variable_undefined?(story_name)
+        raise ArgumentError, "please pass a pivotal story name"
+      end
+
+      if env_variable_undefined?(project_id)
+        raise ArgumentError, "You need to populate the PIVOTAL_PROJECT_ID environment variable"
+      end
+
+      if env_variable_undefined?(pivotal_token)
+        raise ArgumentError, "You need to populate the PIVOTAL_TOKEN environment variable"
+      end
+    end
+
+    def env_variable_undefined?(variable)
+      variable.nil? || variable.empty?
+    end
+
+    def pivotal_project
+      PivotalProject.new(pivotal_token, project_id)
+    end
+
+    def derive_story_owners
+      begin
+        hitch_config = YAML.load_file("#{ENV['HOME']}/.hitchrc")
+        if hitch_config[:current_pair].empty?
+          Array(ENV['USER'])
+        else
+          hitch_config[:current_pair]
+        end
+      rescue
+        Array(ENV['USER'])
+      end
+    end
+
+    def branch_name(story_id)
+      Shellwords.shellescape("#{story_id}-#{story_name.parameterize}")
+    end
+  end
+end

data/lib/git_flower/version.rb

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

metadata

@@ -0,0 +1,196 @@
+--- !ruby/object:Gem::Specification
+name: git_flower
+version: !ruby/object:Gem::Version
+  version: 0.1.1
+platform: ruby
+authors:
+- Alex Wilkinson
+autorequire: 
+bindir: exe
+cert_chain: []
+date: 2017-07-11 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: bundler
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.15'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.15'
+- !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'
+- !ruby/object:Gem::Dependency
+  name: byebug
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+- !ruby/object:Gem::Dependency
+  name: git
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 1.3.0
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 1.3.0
+- !ruby/object:Gem::Dependency
+  name: thor
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 0.19.4
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 0.19.4
+- !ruby/object:Gem::Dependency
+  name: activesupport
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 5.1.2
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 5.1.2
+- !ruby/object:Gem::Dependency
+  name: faraday
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 0.9.0
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 0.9.0
+- !ruby/object:Gem::Dependency
+  name: tracker_api
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - '='
+      - !ruby/object:Gem::Version
+        version: 0.2.9
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - '='
+      - !ruby/object:Gem::Version
+        version: 0.2.9
+description: This library starts features and hotfixes using the git-flow branching
+  model and creates corresponding features and bugs on PivotalTracker using the Pivotal
+  API.
+email:
+- alex.wilkinson@me.com
+executables:
+- git-flower
+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/git-flower
+- git_flower.gemspec
+- lib/git_flower.rb
+- lib/git_flower/cli.rb
+- lib/git_flower/feature-cli.rb
+- lib/git_flower/feature.rb
+- lib/git_flower/git_repository.rb
+- lib/git_flower/hotfix-cli.rb
+- lib/git_flower/hotfix.rb
+- lib/git_flower/pivotal_project.rb
+- lib/git_flower/story.rb
+- lib/git_flower/version.rb
+homepage: https://gitlab.com/alexwilkinson/git-flower
+licenses:
+- MIT
+metadata: {}
+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.12
+signing_key: 
+specification_version: 4
+summary: A CLI for starting git-flow features and hotfixes on PivotalTracker.
+test_files: []