git_tracker 1.3.0 → 1.3.1

data/CHANGELOG.md

@@ -0,0 +1,58 @@
+### dev
+[full changelog](https://github.com/highgroove/git_tracker/compare/v1.3.0...master)
+
+### 1.3.1 / 2012-04-23
+[full changelog](https://github.com/highgroove/git_tracker/compare/v1.3.0...v1.3.1)
+
+Bug fixes
+
+* Bring back fourth Pivotal Tracker keyword, `delivered`
+
+### 1.3.0 / 2012-04-23
+[full changelog](https://github.com/highgroove/git_tracker/compare/v1.2.0...v1.3.0)
+
+Enhancements
+
+* Allow all three Pivotal Tracker keyword states: `fixed`, `completed`, and `finished`
+
+Bug fixes
+
+* Pivotal Tracker keywords are case-insensitive
+
+### 1.2.0 / 2012-04-21
+[full changelog](https://github.com/highgroove/git_tracker/compare/v1.1.0...v1.2.0)
+
+Enhancements
+
+* Allow Pivotal Tracker keyword states: `Delivers` and `Fixes` [KensoDev](https://github.com/KensoDev)
+
+Bug fixes
+
+* Exit with non-zero status code when a commit exists [issue
+  #3](https://github.com/highgroove/git_tracker/issues/3)
+* Exit with non-zero status code with not in a Git repository
+
+### 1.1.0 / 2012-04-03
+[full changelog](https://github.com/highgroove/git_tracker/compare/v1.0.0...v1.1.0)
+
+Enhancements
+
+* The hash preceding the story number is optional [CraigWilliams](https://github.com/CraigWilliams)
+
+Bug fixes
+
+* Fix case-sensitivity issue w/English library
+* Exit with non-zero status code with not in a Git repository [issue
+  #1](https://github.com/highgroove/git_tracker/issues/1)
+
+### 1.0.0 / 2012-03-31
+[full changelog](https://github.com/highgroove/git_tracker/compare/v0.0.1...v1.0.0)
+
+Enhancements
+
+* Hook can install itself in a Git repository
+
+### 0.0.1 / 2012-03-23
+[full changelog](https://github.com/highgroove/git_tracker/compare/5fbbe061e721c1f86fdd5d78a4bfb4c61a0eaf5c...v0.0.1)
+
+* Initial release

data/README.md

@@ -106,8 +106,9 @@ Results in this commit message:
 ### Keywords
 You can use the custom keywords that Pivotal Tracker provide with the API.
 
-The keywords are `fixed`, `completed`, and `finshed` in square brackets. You
-may also use different cases forms of these verbs, such as `Fix` or `FIXES`.
+The keywords are `fixed`, `completed`, `finshed`, and `delivered` in square
+brackets. You may also use different cases forms of these verbs, such as `Fix`
+or `FIXES`.
 
 If you use those keywords in your commit message, the keyword will be prepended
 to the story ID in the commit message.

data/lib/git_tracker/commit_message.rb

@@ -11,7 +11,7 @@ module GitTracker
     end
 
     def keyword
-      @message =~ /\[(fix|fixes|fixed|complete|completes|completed|finish|finishes|finished)\]/io
+      @message =~ /\[(fix|fixes|fixed|complete|completes|completed|finish|finishes|finished|deliver|delivers|delivered)\]/io
       $1
     end
 

data/lib/git_tracker/version.rb

@@ -1,3 +1,3 @@
 module GitTracker
-  VERSION = '1.3.0'
+  VERSION = '1.3.1'
 end

data/spec/git_tracker/commit_message_spec.rb

@@ -17,7 +17,7 @@ describe GitTracker::CommitMessage do
   end
 
   describe '#keyword' do
-    %w[fix Fixed FIXES Complete completed completes FINISH finished Finishes].each do |keyword|
+    %w[fix Fixed FIXES Complete completed completes FINISH finished Finishes Deliver delivered DELIVERS].each do |keyword|
       it "detects the #{keyword} keyword" do
         stub_commit_message("Did the darn thing. [#{keyword}]")
         subject.keyword.should == keyword

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: git_tracker
 version: !ruby/object:Gem::Version
-  version: 1.3.0
+  version: 1.3.1
   prerelease: 
 platform: ruby
 authors:
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2012-04-23 00:00:00.000000000 Z
+date: 2012-04-24 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rspec
@@ -103,6 +103,7 @@ files:
 - .gitignore
 - .rspec
 - .travis.yml
+- CHANGELOG.md
 - Gemfile
 - LICENSE
 - README.md