git-pivotal-tracker 0.9.0

data/.gitignore

@@ -0,0 +1,5 @@
+pkg
+coverage
+*.gem
+*.swp
+tmp

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,45 @@
+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,74 @@
+PATH
+  remote: .
+  specs:
+    git-pivotal-tracker (0.9.0)
+      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)
+    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.2)
+    metaclass (0.0.1)
+    mime-types (1.18)
+    mocha (0.10.5)
+      metaclass (~> 0.0.1)
+    multi_json (1.2.0)
+    nokogiri (1.5.2)
+    pivotal-tracker (0.5.1)
+      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)
+    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)
+    term-ansicolor (1.0.7)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  aruba
+  cucumber
+  git-pivotal-tracker!
+  mocha
+  rake
+  rspec
+  simplecov

data/LICENSE

@@ -0,0 +1,21 @@
+The MIT License
+
+Copyright (c) 2010 Jeff Tucker
+
+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,24 @@
+require 'rubygems'
+require 'rake'
+
+$LOAD_PATH.unshift('lib')
+
+task :default => [:spec, :features]
+
+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
+
+begin
+  require 'cucumber/rake/task'
+  Cucumber::Rake::Task.new(:features) do |t|
+    t.cucumber_opts = "features --format pretty"
+  end
+rescue LoadError => e
+  puts "Cucumber not installed"
+end

data/VERSION

@@ -0,0 +1 @@
+0.9.0

data/bin/git-accept

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

data/bin/git-block

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

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/bin/git-unblock

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

data/features/accept.feature

@@ -0,0 +1,140 @@
+Feature: git accept
+
+  In order to accept a card the following commands:
+  
+    git accept 
+    git accept <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:
+    * mark the card as accepted in Pivotal
+    * push the topic branch to origin
+    * switch to main integration branch, run git pull, then merge in topic branch
+    * push main integration branch
+    * (TODO) delete topic branch is everything previously was done cleanly
+
+  Related git configuration settings:
+    * pivotal.integration-branch - this is where accepted cards are merged. Defaults to master.
+
+  Background:
+    Given I have a finished Pivotal Tracker feature
+    And I am on the "CURRENT_CARD-feature" branch
+
+  Scenario: Executing with no settings
+    When I run `git-accept`
+    Then the output should contain:
+      """
+      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-accept -k PIVOTAL_API_KEY -p PIVOTAL_TEST_PROJECT`
+    Then the output should contain:
+      """
+      Marking Story CURRENT_CARD as accepted...
+      Pushing CURRENT_CARD-feature to origin
+      Pulling master...
+      Merging CURRENT_CARD-feature into master
+      Pushing master to origin
+      Now on master.
+      """
+    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-accept -k PIVOTAL_API_KEY -p PIVOTAL_TEST_PROJECT`
+    Then the output should contain:
+      """
+      Marking Story CURRENT_CARD as accepted...
+      Pushing CURRENT_CARD-feature to origin
+      Pulling master...
+      Merging CURRENT_CARD-feature into master
+      Pushing master to origin
+      Now on master.
+      """
+    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-accept -k PIVOTAL_API_KEY -p PIVOTAL_TEST_PROJECT`
+    Then the output should contain:
+      """
+      Branch name must contain a Pivotal Tracker story id
+      """
+    And the exit status should be 1
+
+  Scenario: Specifying an integration branch in Git configuration
+    Given I have a "release" branch
+    And a file named ".gitconfig" with:
+      """
+      [pivotal]
+        api-token = PIVOTAL_API_KEY
+        full-name = PIVOTAL_USER
+        integration-branch = release
+        project-id = PIVOTAL_TEST_PROJECT
+      """
+    When I run `git-accept -k PIVOTAL_API_KEY -p PIVOTAL_TEST_PROJECT`
+    Then the output should contain:
+      """
+      Marking Story CURRENT_CARD as accepted...
+      Pushing CURRENT_CARD-feature to origin
+      Pulling release...
+      Merging CURRENT_CARD-feature into release
+      Pushing release to origin
+      Now on release.
+      """
+    And I should be on the "release" branch
+
+  Scenario Outline: Accepting cards in an acceptable state
+    Given I have configured the Git repos for Pivotal
+    And the card is a <card_type>
+    And the <card_type> is <card_state>
+    When I run `git-accept -k PIVOTAL_API_KEY -p PIVOTAL_TEST_PROJECT`
+    Then the output should contain:
+      """
+      Marking Story CURRENT_CARD as accepted...
+      Pushing CURRENT_CARD-feature to origin
+      Pulling master...
+      Merging CURRENT_CARD-feature into master
+      Pushing master to origin
+      Now on master.
+      """
+    And I should be on the "master" branch
+    
+    Examples:
+      | card_type | card_state |
+      | chore     | accepted   |
+      | bug       | finished   |
+      | bug       | delivered  |
+      | feature   | finished   |
+      | feature   | delivered  |
+  
+  Scenario Outline: You can't accept cards that aren't ready to be accepted
+    Given I have configured the Git repos for Pivotal
+    And the card is a <card_type>
+    And the <card_type> is <card_state>
+    When I run `git-accept -k PIVOTAL_API_KEY -p PIVOTAL_TEST_PROJECT`
+    Then the output should contain:
+      """
+      Story is not in an acceptable state. It's currently <card_state>.
+      """
+    And I should be on the "CURRENT_CARD-feature" branch
+
+    Examples:
+      | card_type | card_state |
+      | bug       | unstarted  |
+      | bug       | started    |
+      | chore     | unstarted  |
+      | feature   | unstarted  |
+      | feature   | started    |
+      | feature   | rejected   |

data/features/block.feature

@@ -0,0 +1,94 @@
+Feature: git block
+
+  In order to get information about a specific card you can issue one of the following 
+  commands:
+
+    git block
+    git block <options>
+    git block <card_id>
+    git block <card_id> <options>
+
+  Supported options:
+    -m <message>    - specify the reason why this is blocked. If not present, will be prompted. Adds this message to the comment as an activity.
+    -k <api_key>    - specify the Pivotal API key to use. Overrides configuration.
+    -p <project_id> - specify the Pivotal project id to use. Overrides configuration.
+    
+  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-block`
+    Then the output should contain:
+      """
+      Pivotal Tracker API Token and Project ID are required
+      """
+    And the exit status should be 1
+    
+  Scenario: Blocking the current topic branch with a message argument
+    Given I have configured the Git repos for Pivotal
+    When I run `git-block -m "We need more information"`
+    Then the output should contain "Story CURRENT_CARD has been blocked."
+    When the current card is refreshed
+    Then the card CURRENT_CARD should have the "blocked" label
+    And the card CURRENT_CARD should have the comment by "PIVOTAL_USER":
+      """
+      Blocked: We need more information
+      """
+
+  Scenario: Blocking the current topic branch and being prompted for a message
+    Given I have configured the Git repos for Pivotal
+    When I run `git-block` interactively
+    When I type "We need more information"
+    Then the output should contain "Story CURRENT_CARD has been blocked."
+    When the current card is refreshed
+    Then the card CURRENT_CARD should have the "blocked" label
+    And the card CURRENT_CARD should have the comment by "PIVOTAL_USER":
+      """
+      Blocked: We need more information
+      """
+
+  Scenario: Blocking a specific card with a message argument
+    Given I have configured the Git repos for Pivotal
+    When I run `git-block CURRENT_CARD -m "We need more information"`
+    Then the output should contain "Story CURRENT_CARD has been blocked."
+    When the current card is refreshed
+    Then the card CURRENT_CARD should have the "blocked" label
+    And the card CURRENT_CARD should have the comment by "PIVOTAL_USER":
+      """
+      Blocked: We need more information
+      """
+
+  Scenario: Blocking a specific card and being prompted for a message
+    Given I have configured the Git repos for Pivotal
+    When I run `git-block CURRENT_CARD` interactively
+    When I type "We need more information"
+    Then the output should contain "Story CURRENT_CARD has been blocked."
+    When the current card is refreshed
+    Then the card CURRENT_CARD should have the "blocked" label
+    And the card CURRENT_CARD should have the comment by "PIVOTAL_USER":
+      """
+      Blocked: We need more information
+      """
+
+  Scenario: Blocking a card that is already blocked
+    Given I have configured the Git repos for Pivotal
+    And the card is labeled "blocked"
+    When I run `git-block CURRENT_CARD -m "We need more information"`
+    Then the output should contain "Story CURRENT_CARD is already blocked."
+    When the current card is refreshed
+    Then the card CURRENT_CARD should not have the comment:
+      """
+      Blocked: We need more information
+      """
+
+  Scenario: Trying to block 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-block -m "this will fail"`
+    Then the output should contain:
+      """
+      No story id was supplied and you aren't on a topic branch!
+      """
+