git-pivotal-tracker-centro 1.0.0.rc1

data/.gitignore

@@ -0,0 +1,6 @@
+pkg
+coverage
+*.gem
+*.swp
+tmp
+.rbenv-version

data/.rspec

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

data/.rvmrc

@@ -0,0 +1 @@
+rvm use 1.9.3

data/.travis.yml

@@ -0,0 +1,3 @@
+rvm:
+  - 1.9.2
+  - 1.9.3

data/CHANGELOG

@@ -0,0 +1,54 @@
+v 0.9.2
+- verbose is now the default, you can turn it off in your git configuration (pivotal.verbose) or via the --no-verbose command line option
+
+v 0.9.1
+- updating git-accept to work with cards that already accepted in Pivotal
+
+v 0.9.0
+- first release of new command set: accept, block, finish, info, start, unblock
+
+v 0.8.1
+- Improve error reporting when interacting with PivotalTracker
+- Add SSL project support [bunnymatic (Mr Rogers)]
+- Improve method of collecting story ID from branch name
+
+v 0.8.0
+- Drop home-rolled PivotalTracker API for pivotal-tracker gem
+- Add Gemfile for easier development
+- Add better test suite with Cucumber and Aruba
+- Add option for appending the branch name (rather than prepending) [Addy
+Naik]
+- Add new `git info` command [Addy Naik]
+
+v 0.2.3
+- Allow the developer to specify the integration branch for git finish [Graeme Mathieson]
+- Fixed bug which prevented chores from finishing successfully [Joshua Vial]
+- Added option to allow only pickup items already assigned to you [Mark Butcher]
+- Fix RestClient version issues
+
+v 0.2.2
+- Added git chore command
+
+v 0.2.1
+- Remove &:to_s shortcut for MRI 1.8.6 compatibility
+- Updated to handle RestClient 1.4
+
+v 0.2.0
+- Added git feature and git bug commands
+- Deprecated git feature
+- Improved XPath reliability for Pivotal API requests [Sam Stokes]
+
+v 0.1.3
+- Fixed bug preventing command line args from being properly interpretted
+
+v 0.1.2
+- Fixed bug introduced in v 0.1.1 which prevented git pick from completing
+
+v 0.1.1
+- Updated git pick to tell Pivotal who owns the picked feature
+- Improved Pivotal Tracker framework write ability
+
+v 0.1.0
+- Initial release
+- Basic framework for reading from Pivotal Tracker
+- git pick utility

data/Gemfile

@@ -0,0 +1,3 @@
+source "http://rubygems.org"
+
+gemspec

data/Gemfile.lock

@@ -0,0 +1,82 @@
+PATH
+  remote: .
+  specs:
+    git-pivotal-tracker-centro (1.0.0.rc1)
+      pivotal-tracker
+
+GEM
+  remote: http://rubygems.org/
+  specs:
+    aruba (0.4.11)
+      childprocess (>= 0.2.3)
+      cucumber (>= 1.1.1)
+      ffi (>= 1.0.11)
+      rspec (>= 2.7.0)
+    builder (3.0.0)
+    childprocess (0.3.1)
+      ffi (~> 1.0.6)
+    coderay (1.0.5)
+    cucumber (1.1.9)
+      builder (>= 2.1.2)
+      diff-lcs (>= 1.1.2)
+      gherkin (~> 2.9.0)
+      json (>= 1.4.6)
+      term-ansicolor (>= 1.0.6)
+    diff-lcs (1.1.3)
+    ffi (1.0.11)
+    gherkin (2.9.3)
+      json (>= 1.4.6)
+    happymapper (0.4.0)
+      libxml-ruby (~> 2.0)
+    json (1.6.6)
+    libxml-ruby (2.3.3)
+    metaclass (0.0.1)
+    method_source (0.7.1)
+    mime-types (1.19)
+    mocha (0.10.5)
+      metaclass (~> 0.0.1)
+    multi_json (1.2.0)
+    nokogiri (1.5.5)
+    pivotal-tracker (0.5.8)
+      builder
+      builder
+      happymapper (>= 0.3.2)
+      happymapper (>= 0.3.2)
+      nokogiri (>= 1.4.3)
+      nokogiri (~> 1.4)
+      rest-client (~> 1.6.0)
+      rest-client (~> 1.6.0)
+    pry (0.9.8.4)
+      coderay (~> 1.0.5)
+      method_source (~> 0.7.1)
+      slop (>= 2.4.4, < 3)
+    rake (0.9.2.2)
+    rest-client (1.6.7)
+      mime-types (>= 1.16)
+    rspec (2.9.0)
+      rspec-core (~> 2.9.0)
+      rspec-expectations (~> 2.9.0)
+      rspec-mocks (~> 2.9.0)
+    rspec-core (2.9.0)
+    rspec-expectations (2.9.0)
+      diff-lcs (~> 1.1.3)
+    rspec-mocks (2.9.0)
+    simplecov (0.6.1)
+      multi_json (~> 1.0)
+      simplecov-html (~> 0.5.3)
+    simplecov-html (0.5.3)
+    slop (2.4.4)
+    term-ansicolor (1.0.7)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  aruba
+  cucumber
+  git-pivotal-tracker-centro!
+  mocha
+  pry
+  rake
+  rspec
+  simplecov

data/LICENSE

@@ -0,0 +1,21 @@
+The MIT License
+
+Copyright (c) 2012 John Wood
+
+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/Rakefile

@@ -0,0 +1,49 @@
+require 'rubygems'
+require 'rake'
+
+# Set up a test Pivotal project for the Cucumber tests to use
+ENV['PIVOTAL_API_KEY'] = "81f09c932c8bfd2b028ec5e52ec7cf47" # your API key
+ENV['PIVOTAL_TEST_PROJECT'] = "681077" # your test project ID (123456)
+ENV['PIVOTAL_USER'] = "John Wood" # Your user name (Joe Smith)
+
+$LOAD_PATH.unshift('lib')
+
+task :default => [:spec, :features]
+
+task :spec do
+  begin
+    require 'rspec/core/rake_task'
+    RSpec::Core::RakeTask.new do |t|
+      t.rspec_opts = ['--color']
+    end
+  rescue LoadError => e
+    puts "RSpec not installed"
+  end
+end
+
+task :features do
+  begin
+    require 'cucumber/rake/task'
+
+    if [ENV['PIVOTAL_API_KEY'], ENV['PIVOTAL_TEST_PROJECT'], ENV['PIVOTAL_USER']].any? { |x| x.nil? || x.empty? }
+      raise "ERROR: API key, test project, and user must be set in the Rakefile for the Cucumber tests to run"
+    end
+
+    Cucumber::Rake::Task.new(:features) do |t|
+      t.cucumber_opts = "features --format pretty"
+    end
+  rescue LoadError => e
+    puts "Cucumber not installed"
+  end
+end
+
+task :install do
+  puts "Uninstalling..."
+  system "gem uninstall -x git-pivotal-tracker-centro"
+
+  puts "Building..."
+  system "gem build  git-pivotal-tracker-centro.gemspec"
+
+  puts "Installing..."
+  system "gem install git-pivotal-tracker-centro-#{IO.read("VERSION")}"
+end

data/VERSION

@@ -0,0 +1 @@
+1.0.0.rc1

data/bin/git-finish

@@ -0,0 +1,7 @@
+#!/usr/bin/env ruby
+
+$LOAD_PATH.unshift File.join(File.dirname(__FILE__), '..', 'lib')
+
+require 'commands/finish'
+
+exit Commands::Finish.new(*ARGV).with(STDIN, STDOUT).run!

data/bin/git-info

@@ -0,0 +1,7 @@
+#!/usr/bin/env ruby
+
+$LOAD_PATH.unshift File.join(File.dirname(__FILE__), '..', 'lib')
+
+require 'commands/info'
+
+exit Commands::Info.new(*ARGV).with(STDIN, STDOUT).run!

data/bin/git-start

@@ -0,0 +1,8 @@
+#!/usr/bin/env ruby
+
+$LOAD_PATH.unshift File.join(File.dirname(__FILE__), '..', 'lib')
+
+require 'commands/start'
+
+args = ARGV
+exit Commands::Start.for(*ARGV).with(STDIN, STDOUT).run!

data/features/finish.feature

@@ -0,0 +1,88 @@
+Feature: git finish
+
+  In order to finish the card for the current topic branch you can issue the following 
+  commands:
+  
+    git finish 
+    git finish <options>
+
+  Supported options:
+    -k <api_key>    - specify the Pivotal API key to use. Overrides configuration.
+    -p <project_id> - specify the Pivotal project id to use. Overrides configuration.
+    
+  This will do the following:
+    * switch to the master branch
+    * delete the local branch
+    * delete the remote branch
+    * mark the card as finished in Pivotal
+
+  Background:
+    Given I have a started Pivotal Tracker feature
+    And I am on the "CURRENT_CARD-feature" branch
+
+  Scenario: Executing with no settings
+    When I run `git-finish --force`
+    Then the output should contain each line:
+      """
+      Pivotal Tracker API Token and Project ID are required
+      """
+    And the exit status should be 1
+
+  Scenario: Executing with inline settings
+    When I run `git-finish -k PIVOTAL_API_KEY -p PIVOTAL_TEST_PROJECT --force`
+    Then the output should contain each line:
+      """
+      Switching to master
+      Destroying local branch
+      Destroying remote branch
+      Marking Story CURRENT_CARD as finished...
+      """
+    And I should be on the "master" branch
+
+  Scenario: Executing with git configuration
+    Given a file named ".gitconfig" with:
+      """
+      [pivotal]
+        api-token = PIVOTAL_API_KEY
+        full-name = PIVOTAL_USER
+        project-id = PIVOTAL_TEST_PROJECT
+      """
+    When I run `git-finish -k PIVOTAL_API_KEY -p PIVOTAL_TEST_PROJECT --force`
+    Then the output should contain each line:
+      """
+      Switching to master
+      Destroying local branch
+      Destroying remote branch
+      Marking Story CURRENT_CARD as finished...
+      """
+    And I should be on the "master" branch
+
+  Scenario: Executing from a misnamed branch
+    Given I am on the "missing-an-id" branch
+    When I run `git-finish -k PIVOTAL_API_KEY -p PIVOTAL_TEST_PROJECT --force`
+    Then the output should contain each line:
+      """
+      Branch name must contain a Pivotal Tracker story id
+      """
+    And the exit status should be 1
+
+  Scenario: Closing chore stories
+    Given I have a started Pivotal Tracker chore
+    And I am on the "CURRENT_CARD-chore" branch
+    And a file named ".gitconfig" with:
+      """
+      [pivotal]
+        api-token = PIVOTAL_API_KEY
+        full-name = PIVOTAL_USER
+        project-id = PIVOTAL_TEST_PROJECT
+      """
+    When I run `git-finish -k PIVOTAL_API_KEY -p PIVOTAL_TEST_PROJECT --force`
+    Then the output should contain each line:
+      """
+      Switching to master
+      Destroying local branch
+      Destroying remote branch
+      Marking Story CURRENT_CARD as finished...
+      """
+    And I should be on the "master" branch
+  

data/features/info.feature

@@ -0,0 +1,99 @@
+Feature: git info
+
+  In order to get information about a specific card you can issue one of the following 
+  commands:
+
+    git info
+    git info <options>
+    git info <card_id>
+    git info <card_id> <options>
+
+  Supported options:
+    --comments      - displays comments for the card
+    -k <api_key>    - specify the Pivotal API key to use. Overrides configuration.
+    -p <project_id> - specify the Pivotal project id to use. Overrides configuration.
+    -D              - do not prompt for user input, use recommended values by default.
+    
+  Background:
+    Given I have a Pivotal Tracker feature named "Test Story" with description "This is the description!"
+    And I am on the "CURRENT_CARD-feature" branch
+
+  Scenario: Executing with no settings
+    When I run `git-info`
+    Then the output should contain each line:
+      """
+      Pivotal Tracker API Token and Project ID are required
+      """
+    And the exit status should be 1
+    
+  Scenario: Grabbing info about current topic branch
+    Given I have configured the Git repos for Pivotal
+    When I run `git-info`
+    Then the output should contain each line:
+      """
+      Story:         Test Story
+      URL:           http://www.pivotaltracker.com/story/show/CURRENT_CARD
+      State:         not accepted
+      Description:
+        This is the description!
+      """
+
+  Scenario: Supplying Pivotal configuration via command line arguments
+    When I run `git-info -k PIVOTAL_API_KEY -p PIVOTAL_TEST_PROJECT -n "PIVOTAL_USER" -D`
+    Then the output should contain each line:
+      """
+      Story:         Test Story
+      URL:           http://www.pivotaltracker.com/story/show/CURRENT_CARD
+      State:         not accepted
+      Description:
+        This is the description!
+      """
+
+  Scenario: Grabbing info about a specific card in question topic branch
+    Given I have a Pivotal Tracker chore named "Test Chore" with description "The chore description!"
+    And I have configured the Git repos for Pivotal
+    When I run `git-info CURRENT_CARD`
+    Then the output should contain each line:
+      """
+      Story:         Test Chore
+      URL:           http://www.pivotaltracker.com/story/show/CURRENT_CARD
+      State:         not accepted
+      Description:
+        The chore description!
+      """
+
+  Scenario: Grabbing info when the card has labels
+    Given I have a Pivotal Tracker chore named "Test Chore" with description "The chore description!"
+    And the chore is labeled "foo, bar, baz"
+    And I have configured the Git repos for Pivotal
+    When I run `git-info CURRENT_CARD`
+    Then the output should contain each line:
+      """
+      Story:         Test Chore
+      URL:           http://www.pivotaltracker.com/story/show/CURRENT_CARD
+      Labels:        bar, baz, foo
+      State:         not accepted
+      Description:
+        The chore description!
+      """
+
+  Scenario: Requesting comments on a card using --comments
+    Given I have a Pivotal Tracker chore named "Test Chore" with description "The chore description!"
+    And the "PIVOTAL_USER" commented on the card "Well, this looks mighty fine!"
+    And I have configured the Git repos for Pivotal
+    When I run `git-info CURRENT_CARD --comments`
+    Then the output should contain "Comments:"
+    And the output should contain "Well, this looks mighty fine!"
+    And the output should contain "PIVOTAL_USER"
+
+  Scenario: Grabbing info when not on a topic branch and not supplying a card id
+    Given I have configured the Git repos for Pivotal
+    And I am on the "foo" branch
+    Then I should be on the "foo" branch
+    When I run `git-info`
+    Then the output should contain each line:
+      """
+      No story id was supplied and you aren't on a topic branch!
+      """
+  
+  

data/features/start.feature

@@ -0,0 +1,113 @@
+Feature: git start
+
+  In order to start the next available card in the project you can issue the following
+  commands:
+     
+     git start <options>
+     git start <card_type> <options>
+
+  Supported options:
+    -k <api_key>    - specify the Pivotal API key to use. Overrides configuration.
+    -p <project_id> - specify the Pivotal project id to use. Overrides configuration.
+    -D              - do not prompt for user input, use recommended values by default.
+    
+  This will check out a topic branch for the card and place you on it.
+  
+  Scenario Outline: Executing with no settings
+    When I run `<command>`
+    Then the output should contain each line:
+      """
+      Pivotal Tracker API Token and Project ID are required
+      """
+    And the exit status should be 1
+  
+    Examples:
+      | command           |
+      | git-start bug     |
+      | git-start chore   |
+      | git-start feature |
+
+  Scenario: Starting the next feature when it is unestimated
+    Given I have an unestimated Pivotal Tracker feature
+    And I have configured the Git repos for Pivotal
+    When I run `git-start feature -D --force`
+    Then the output should contain each line:
+      """
+      Stories in the started state must be estimated.
+      """
+    And the exit status should be 1
+
+  # Assumption: that chores can be started without being estimated in Pivotal
+  Scenario: Starting the next chore when it is unestimated
+    Given I have an unestimated Pivotal Tracker chore
+    And I have configured the Git repos for Pivotal
+    When I run `git-start chore -D --force`
+    Then the output should contain "Switched to a new branch 'CURRENT_CARD-a-chore'"
+    And I should be on the "CURRENT_CARD-a-chore" branch
+    And card CURRENT_CARD is marked is started in Pivotal Tracker
+
+  # Assumption: that estimating bugs in Pivotal is turned off
+  Scenario: Starting the next bug when it is unestimated
+    Given I have an unestimated Pivotal Tracker bug
+    And I have configured the Git repos for Pivotal
+    When I run `git-start bug -D --force`
+    Then the output should contain "Switched to a new branch 'CURRENT_CARD-a-bug'"
+    And I should be on the "CURRENT_CARD-a-bug" branch
+    And card CURRENT_CARD is marked is started in Pivotal Tracker
+
+  Scenario Outline: Starting the next estimated card interactively (without -D option)
+    Given I have a Pivotal Tracker <card_type>
+    And I have configured the Git repos for Pivotal
+    When I run `git-start <card_type> --force` interactively
+    And I type "a_purple_<card_type>"
+    Then the output should contain "Switched to a new branch 'a_purple_<card_type>'"
+    And I should be on the "a_purple_<card_type>" branch
+    And card CURRENT_CARD is marked is started in Pivotal Tracker
+    
+    Examples:
+      | card_type |
+      | bug       |
+      | chore     |
+      | feature   |
+
+  Scenario Outline: Starting the next estimated card using configured defaults (with -D option)
+    Given I have a Pivotal Tracker <card_type>
+    And I have configured the Git repos for Pivotal
+    When I run `git-start <card_type> -D --force`
+    Then the output should contain "Switched to a new branch 'CURRENT_CARD-a-<card_type>'"
+    And I should be on the "CURRENT_CARD-a-<card_type>" branch
+    And card CURRENT_CARD is marked is started in Pivotal Tracker
+    
+    Examples:
+      | card_type | branch_suffix |
+      | bug       |     fix       |
+      | chore     |               |
+      | feature   |               |
+
+  Scenario Outline: Starting a specific card
+    Given I have a Pivotal Tracker <card_type>
+    And I have configured the Git repos for Pivotal
+    When I run `git-start CURRENT_CARD -D --force`
+    Then the output should contain "Switched to a new branch 'CURRENT_CARD-a-<card_type>'"
+    And I should be on the "CURRENT_CARD-a-<card_type>" branch
+    And card CURRENT_CARD is marked is started in Pivotal Tracker
+    
+    Examples:
+      | card_type | branch_suffix |
+      | bug       |     fix       |
+      | chore     |               |
+      | feature   |               |
+
+  Scenario Outline: Supplying Pivotal configuration via command line arguments
+    Given I have a Pivotal Tracker <card_type>
+    And I have configured the Git repos for Pivotal with bogus information
+    When I run `git-start <card_type> -k PIVOTAL_API_KEY -p PIVOTAL_TEST_PROJECT -n "PIVOTAL_USER" -D --force`
+    Then the output should contain "Switched to a new branch 'CURRENT_CARD-a-<card_type>'"
+    And I should be on the "CURRENT_CARD-a-<card_type>" branch
+    And card CURRENT_CARD is marked is started in Pivotal Tracker
+
+    Examples:
+      | card_type | branch_suffix |
+      | bug       |     fix       |
+      | chore     |               |
+      | feature   |               |

data/features/step_definitions/steps.rb

@@ -0,0 +1,119 @@
+STORY_TYPE = /feature|bug|chore|release/
+STORY_STATE = /unscheduled|unstarted|started|finished|delivered|accepted|rejected/
+
+Transform /PIVOTAL|CURRENT/ do |placeholder|
+  placeholder.
+    gsub("PIVOTAL_API_KEY", ENV['PIVOTAL_API_KEY']).
+    gsub("PIVOTAL_TEST_PROJECT", ENV['PIVOTAL_TEST_PROJECT']).
+    gsub("PIVOTAL_USER", ENV['PIVOTAL_USER']).
+    gsub("CURRENT_CARD", current_card.id.to_s)
+end
+
+Given "I debug" do
+  require 'pry'
+  binding.pry
+end
+
+Given /^I have configured the Git repos for Pivotal$/ do
+  step %|a file named ".gitconfig" with:|, <<-EOT.gsub!(/^\s+\S/, '')
+    |[pivotal]
+    |  api-token = PIVOTAL_API_KEY
+    |  full-name = PIVOTAL_USER
+    |  project-id = PIVOTAL_TEST_PROJECT
+    |  verbose    = false
+  EOT
+end
+
+Given /^I have configured the Git repos for Pivotal with bogus information$/ do
+  step %|a file named ".gitconfig" with:|, <<-EOT.gsub!(/^\s+\S/, '')
+    |[pivotal]
+    |  api-token          = badtoken
+    |  full-name          = Bad Joe
+    |  project-id         = something
+    |  remote             = origin
+    |  verbose            = false
+  EOT
+end
+
+Given /^the "([^"]+)" commented on the card "([^"]+)"$/ do |author, text|
+  comment_on_story :author => author, :text => text
+end
+
+Given /^the (#{STORY_TYPE}|card) is labeled "([^"]+)"$/ do |type, labels|
+  update_test_story :labels => labels
+end
+
+Given /^I have a(?:n)? (#{STORY_STATE})?\s?Pivotal Tracker (#{STORY_TYPE})$/ do |status, type|
+  options = {}
+  options[:current_state] = status if status
+  create_test_story type, options
+end
+
+Given /^I have a(?:n)? unestimated \s?Pivotal Tracker (#{STORY_TYPE})$/ do |type|
+  options = { :estimate => -1 }
+  create_test_story type, options
+end
+
+Given /^I have a(?:n)? (#{STORY_STATE})?\s?Pivotal Tracker (#{STORY_TYPE}) named "([^"]+)" with description "([^"]+)"$/ do |status, type, name, description|
+  options = { :name => name, :description => description }
+  options[:current_state] = status if status
+  create_test_story type, options
+end
+
+Given /the card is a (#{STORY_TYPE})/ do |type|
+  update_test_story :story_type => type
+end
+
+Given /the (#{STORY_TYPE}) is unestimated/ do |type|
+  update_test_story :estimate => -1
+end
+
+Given /the (#{STORY_TYPE}) is (#{STORY_STATE})/ do |type, state|
+  update_test_story :current_state => state
+end
+
+Given /^I am on the "([^"]*)" branch$/ do |branch|
+  `git checkout -b #{branch} > /dev/null 2>&1`
+end
+
+Given /^I have a "([^"]*)" branch$/ do |branch|
+  `git branch #{branch} > /dev/null 2>&1`
+end
+
+When /^the current card is refreshed$/ do
+  refresh_current_card!
+end
+
+Then /^the card CURRENT_CARD should (not )?have the "([^"]*)" label$/ do |negate, label|
+  if negate
+    current_card.labels.to_s.should_not include(label)
+  else
+    current_card.labels.to_s.should include(label)
+  end
+end
+
+Then /^the card CURRENT_CARD should have the comment by "([^"]*)":$/ do |author, str|
+  current_card.notes.all.last.tap do |note|
+    note.author.should eq(author)
+    note.text.should include(str)
+  end
+end
+
+Then /^the card CURRENT_CARD should not have the comment:$/ do |str|
+  current_card.notes.all.detect{ |n| n.text.include?(str) }.should be_nil
+end
+
+
+Then /^I should be on the "([^"]*)" branch$/ do |branch|
+  current_branch.should == branch
+end
+
+Then /^card (CURRENT_\w+) is marked is started in Pivotal Tracker$/ do |card_id|
+  assert_card_is_started(card_id)
+end
+
+Then /^the output should contain each line:$/ do |str|
+  str.split("\n").each do |line|
+    assert_partial_output(line, all_output)
+  end
+end