pivotal-github 0.8.0 → 0.8.1

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 0ec9bc112f32b279089cbca37fa39bcd8a72bc07
+  data.tar.gz: dc07621e400fc821a175df1e928ff4c31e6c4193
+SHA512:
+  metadata.gz: 0580d4c0e1175daf5cee0f09c69561bca87c6c2eefc20065666424d52c9e0391f0dbb8ff609aefcf9f9fee00fee561c6731b8af98025ca812b9f9f108076623d
+  data.tar.gz: c731e0102496125328146b8514c3c366306e32c0a063df1abd120ca4ea76d7f6f0e4add67489998db5a11397ccb201cf76010ddf52d8fbb4437cd38739989f7d

data/.ruby-version

@@ -1 +1 @@
-ruby-1.9.3-p392
+ruby-2.0.0

data/Gemfile

@@ -1,6 +1,7 @@
 source 'https://rubygems.org'
+ruby '2.0.0'
 
-gem 'rspec', '~> 2.12.0'
+gem 'rspec', '~> 2.13.0'
 gem 'httparty', '~> 0.10.0'
 
 # Specify your gem's dependencies in pivotal-github.gemspec

data/README.md

@@ -1,6 +1,6 @@
 # pivotal-github
 
-The `pivotal-github` gem facilitates a [Pivotal Tracker](http://pivotaltracker.com/)–[GitHub](http://github.com/) workflow inspired by the workflow used by [Logical Reality](http://lrdesign.com/). (Despite its name, `pivotal-github` also works fine with [BitBucket](http://bitbucket.com/); see **Configuration** below.) As per usual, there are several projects (notably [git-flow](https://github.com/nvie/gitflow) and [git-pivotal](https://github.com/trydionel/git-pivotal)) that implement similar solutions, but none met my exact needs, so I rolled my own.
+The `pivotal-github` gem facilitates a [Pivotal Tracker](http://pivotaltracker.com/)–[GitHub](http://github.com/) workflow inspired by the workflow used by [Logical Reality](http://lrdesign.com/). (Despite its name, `pivotal-github` also works fine with [Bitbucket](http://bitbucket.com/); see **Configuration** below.) As per usual, there are several projects (notably [git-flow](https://github.com/nvie/gitflow) and [git-pivotal](https://github.com/trydionel/git-pivotal)) that implement similar solutions, but none met my exact needs, so I rolled my own.
 
 ## Installation
 
@@ -14,7 +14,7 @@ The full workflow described herein requires some of the Git utilities from [git-
 
 The `pivotal-github` gem adds several additional Git commands to the local environment. The main addition, `git story-commit`, automatically incorporates the Pivotal Tracker story id(s) into the commit messages, while adding options to mark the story **Finished** or **Delivered**.
 
-The `git story-commit` command makes the assumption that any string of digits in the branch name is a story id. This means that the branch names `6283185-add-markdown-support`, `6283185_add_markdown_support`, and `add-markdown-support-6283185` all correspond to story id `6283185`, while `add-things-6283185-3141592` corresponds to both `6283185` *and* `3141592`.
+The `git story-commit` command makes the assumption that any string of eight or more digits in the branch name is a story id. (As of this writing, Pivotal Tracker ids are eight digits long, so shorter digit strings aren't valid ids.) This means that the branch names `62831853-add-markdown-support`, `62831853_add_markdown_support`, `add-markdown-support-62831853`, and `rails_4_0_62831853` all correspond to story id `62831853`, while `add-things-62831853-31415926` corresponds to both `62831853` *and* `31415926`.
 
 The full set of commands is as follows:
 
@@ -22,16 +22,16 @@ The full set of commands is as follows:
 
 `git story-commit` makes a standard `git commit` with the story number added to the commit message. This automatically adds a link at Pivotal Tracker between the story and the diff when the branch gets pushed up to GitHub.
 
-For example, when on a branch called `add-markdown-support-6283185`, the `git story-commit` command automatically adds `[#6283185]` to the commit message:
+For example, when on a branch called `add-markdown-support-62831853`, the `git story-commit` command automatically adds `[#62831853]` to the commit message:
 
     $ git story-commit -am "Add foo bars"
-	[add-markdown-support-6283185 6f56414] Add foo bars
+	[add-markdown-support-62831853 6f56414] Add foo bars
 
 The commit message is multiline and includes the story id:
 
     Add foo bars
 
-    [#6283185]
+    [#62831853]
 
 (Previous versions of `pivotal-github` put the story id on the same line as the commit summary (per the usage at the [Pivotal Tracker API](https://www.pivotaltracker.com/help/api?version=v3)), but placing it in a separate line gives the user direct control over the length of the message. It also looks less cluttered.)
 
@@ -43,7 +43,7 @@ This gives the message
 
     Remove baz quuxes
 
-    [Finishes #6283185]
+    [Finishes #62831853]
 
 To mark a story as **Delivered**, add the `-d` flag:
 
@@ -53,22 +53,22 @@ The message in this case is
 
     Remove baz quuxes
 
-    [Delivers #6283185]
+    [Delivers #62831853]
 
 Either the `-f` flag or the `-d` flag can be combined with other flags, yielding commands like
 
     $ git story-commit -dam "Remove baz quuxes"
 
-`git story commit` supports multiple story numbers as well. For example, with a branch called `add-things-6283185-3141592`, we could deliver both stories as follows:
+`git story commit` supports multiple story numbers as well. For example, with a branch called `add-things-62831853-31415926`, we could deliver both stories as follows:
 
     $ git story-commit -dam "Remove baz quuxes"
-	[add-things-6283185-3141592 7g56429] Remove baz quuxes
+	[add-things-62831853-31415926 7g56429] Remove baz quuxes
 
 The message here is
 
     Remove baz quuxes
 
-    [Delivers #6283185 #3141592]
+    [Delivers #62831853 #31415926]
 
 #### Options
 
@@ -84,10 +84,10 @@ Additionally, `git story-commit` accepts any options valid for `git commit`. (`g
 
 ### git story-merge
 
-`git story-merge` merges the current branch into `master`. On a branch called `add-markdown-support-6283185`, `git story-merge` is equivalent to the following:
+`git story-merge` merges the current branch into `master`. On a branch called `add-markdown-support-62831853`, `git story-merge` is equivalent to the following:
 
     $ git checkout master
-    $ git merge --no-ff --log add-markdown-support-6283185
+    $ git merge --no-ff --log add-markdown-support-62831853
 
 Note that this effectively changes the default merge behavior from fast-forward to no-fast-forward, which makes it possible to use `git log` to see which of the commit objects together have implemented a story. As noted in [A successful Git branching model](http://nvie.com/posts/a-successful-git-branching-model/),
 
@@ -110,11 +110,11 @@ Additionally, `git story-merge` accepts any options valid for `git merge`.
 
 ### git story-pull-request
 
-`git story-pull-request` opens the proper remote URI to issue a pull request for the current branch (OS X–only):
+`git story-pull-request` opens the proper remote URL to issue a pull request for the current branch (OS X–only):
 
     $ git story-pull-request
 
-By default, `git story-pull-request` issues a `git push-branch` as well, just in case the local branch hasn't yet been pushed up to the remote repository. 
+By default, `git story-pull-request` issues a `git push-branch` as well (from [git-utils](https://github.com/mhartl/git-utils)), just in case the local branch hasn't yet been pushed up to the remote repository.
 
 As with `git story-merge`, by default `git story-pull-request` exits with a warning if the most recent commit doesn't finish the story.
 
@@ -126,14 +126,14 @@ As with `git story-merge`, by default `git story-pull-request` exits with a warn
 
 ### story-open
 
-The `story-open` command (*note*: no `git`) opens the current story in the default browser (OS X–only):
+The `story-open` command (no `git`) opens the current story in the default browser (OS X–only):
 
     $ story-open
 
 
 ## Configuration
 
-In order to use the `pivotal-github` gem, you need to configure a post-receive hook for your repository. At GitHub, navigate to `Settings > Service Hooks > Pivotal Tracker` and paste in your Pivotal Tracker API token. (To find your Pivotal Tracker API token, go to your user profile and scroll to the bottom.) Be sure to check the **Active** box to activate the post-receive hook. At BitBucket, click on the gear icon to view the settings, click on `Services`, select `Pivotal Tracker`, and paste in your Pivotal Tracker API key.
+In order to use the `pivotal-github` gem, you need to configure a post-receive hook for your repository. At GitHub, navigate to `Settings > Service Hooks > Pivotal Tracker` and paste in your Pivotal Tracker API token. (To find your Pivotal Tracker API token, go to your user profile and scroll to the bottom.) Be sure to check the **Active** box to activate the post-receive hook. At Bitbucket, click on the gear icon to view the settings, click on `Services`, select `Pivotal Tracker`, and paste in your Pivotal Tracker API key.
 
 The `pivotal-github` command names follow the Git convention of being verbose (e.g., unlike Subversion, Git doesn't natively support `co` for `checkout`), but I recommend setting up aliases as necessary. Here are some suggestions, formatted so that they can be pasted directly into a terminal window:
 
@@ -147,7 +147,7 @@ I also recommend setting up an alias for `git push-branch` from [git-utils](http
 
 A single-developer workflow would then look like this:
 
-    $ git co -b add-markdown-support-6283185
+    $ git co -b add-markdown-support-62831853
     $ git pb
     <work>
     $ git sc -am "Added foo"
@@ -161,6 +161,8 @@ A single-developer workflow would then look like this:
     $ git rebase master
     $ git sm
 
+Here `git sync` is also from [git-utils](https://github.com/mhartl/git-utils).
+
 ## Workflow with integrated code reivew
 
 The `pivotal-github` gem is degined to support a workflow involving integrated code review, which has the usual benefits: at least two pairs of eyes see any committed code, and at least two brains know basically what the committed code does. The cost is that having a second developer involved can slow you down. I suggest using your judgment to determine which workflow makes the most sense on a story-by-story basis.
@@ -170,11 +172,11 @@ Here's the process in detail:
 ### Developer #1 (Alice)
 
 1. Start an issue at [Pivotal Tracker](http://pivotaltracker.com/) and copy the story id to your buffer
-2. Create a branch in the local Git repository containing the story id and a brief description: `git checkout -b add-markdown-support-6283185`
+2. Create a branch in the local Git repository containing the story id and a brief description: `git checkout -b add-markdown-support-62831853`
 3. Create a remote branch at [GitHub](http://github.com/) using `git push-branch`
 3. Use `git story-commit` to make commits, which includes the story number in the commit message: `git story-commit -am "Add syntax highlighting"`
 4. Continue pushing up after each commit using `git push` as usual
-4. When done with the story, add `-f` to mark the story as **Finished** using `git story-commit -f -am "Add paragraph breaks"` or as **Delivered** using `git story-commit -d -am "Add paragraph breaks"`
+4. When done with the story, add `-f` to mark the story as **Finished** using `git story-commit -fam "Add paragraph breaks"` or as **Delivered** using `git story-commit -dam "Add paragraph breaks"`
 4. Rebase against `master` using `git sync` followed by `git rebase master` or `git rebase master --interactive` (optionally squashing commit messages as described in the article [A Git Workflow for Agile Teams](http://reinh.com/blog/2009/03/02/a-git-workflow-for-agile-teams.html))
 4. Push up with `git push`
 6. At the GitHub page for the repo, select **Branches** and submit a pull request

data/lib/pivotal-github/command.rb

@@ -27,12 +27,12 @@ class Command
 
   # Returns the story id (or ids).
   # We extract the story id(s) from the branch name, so that, e.g.,
-  # the branch `add-markdown-support-6283185` gives story_id '6283185'.
+  # the branch `add-markdown-support-62831853` gives story_id '62831853'.
   # New as of version 0.7, we support multiple story ids in a single
-  # branch name, so that `add-markdown-support-6283185-3141592` can be used
-  # to update story 6283185 and story 3141592 simultaneously.
+  # branch name, so that `add-markdown-support-62831853-31415926` can be used
+  # to update story 62831853 and story 31415926 simultaneously.
   def story_ids
-    story_branch.scan(/\d+/)
+    story_branch.scan(/[0-9]{8,}/)
   end
 
   # Returns the single story id for the common case of one id.

data/lib/pivotal-github/story_commit.rb

@@ -38,8 +38,8 @@ class StoryCommit < Command
 
   # Returns the story ids formatted for story commits.
   # For single-id stories, this is just the number preceded by '#', as in
-  # '#6283185'. For multiple-id stories, each story id is precede by '#', as in
-  # '#6283185 #3141592'
+  # '#62831853'. For multiple-id stories, each story id is precede by '#', as in
+  # '#62831853 #31415926'
   def message_ids
     story_ids.map { |id| "##{id}" }.join(' ')
   end

data/lib/pivotal-github/story_open.rb

@@ -3,7 +3,7 @@ require 'pivotal-github/command'
 class StoryOpen < Command
 
   # Returns a command appropriate for executing at the command line
-  # I.e., 'open https://www.pivotaltracker.com/story/show/6283185'
+  # I.e., 'open https://www.pivotaltracker.com/story/show/62831853'
   def cmd
     story_ids.map do |id|
       "open https://www.pivotaltracker.com/story/show/#{id}"

data/lib/pivotal-github/story_pull_request.rb

@@ -16,7 +16,7 @@ class StoryPullRequest < FinishedCommand
   end
 
   # Returns a command appropriate for executing at the command line
-  # I.e., 'open https://www.pivotaltracker.com/story/show/6283185'
+  # I.e., 'open https://www.pivotaltracker.com/story/show/62831853'
   def cmd
     "git pull-request"
   end

data/lib/pivotal-github/version.rb

@@ -1,5 +1,5 @@
 module Pivotal
   module Github
-    VERSION = "0.8.0"
+    VERSION = "0.8.1"
   end
 end

data/spec/commands/command_spec.rb

@@ -2,20 +2,33 @@ require 'spec_helper'
 
 describe Command do
   let(:command) { Command.new }
-  before { command.stub(:story_branch).and_return('6283185-tau-manifesto') }
+  before { command.stub(:story_branch).and_return('62831853-tau-manifesto') }
   subject { command }
 
   it { should respond_to(:cmd) }
   it { should respond_to(:args) }
   it { should respond_to(:options) }
   it { should respond_to(:parse) }
+  it { should respond_to(:story_id) }
   it { should respond_to(:story_ids) }
-  its(:story_ids) { should eq ['6283185']}
+
+  its(:story_id)  { should eq  '62831853'  }
+  its(:story_ids) { should eq ['62831853'] }
 
   describe "branches with multiple stories" do
     before do
-      command.stub(:story_branch).and_return('6283185-tau-manifesto-3141592')
+      command.stub(:story_branch).and_return('62831853-tau-manifesto-31415926')
     end
-    its(:story_ids) { should eq ['6283185', '3141592'] }
+    its(:story_ids) { should eq ['62831853', '31415926'] }
+  end
+
+  describe "when the branch name has other digit strings shorter than 8" do
+    before { command.stub(:story_branch).and_return('3141592-62831853') }
+    its(:story_id) { should eq '62831853' }
+  end
+
+  describe "with a story id with more than 8 digits" do
+    before { command.stub(:story_branch).and_return('628318530-tau-manifesto') }
+    its(:story_id) { should eq '628318530' }
   end
 end

data/spec/commands/story_commit_spec.rb

@@ -3,7 +3,7 @@ require 'spec_helper'
 describe StoryCommit do
 
   let(:command) { StoryCommit.new(['-m', 'msg', '-a', '-z', '--foo']) }
-  before { command.stub(:story_branch).and_return('6283185-tau-manifesto') }
+  before { command.stub(:story_branch).and_return('62831853-tau-manifesto') }
   subject { command }
 
   it { should respond_to(:message) }
@@ -11,7 +11,7 @@ describe StoryCommit do
   shared_examples "story-commit with known options" do
     subject { command }
 
-    its(:cmd)      { should =~ /git commit/ }
+    its(:cmd)      { should match /git commit/ }
     its(:message)  { should_not be_empty }
     its(:message?) { should be_true }
     its(:all?)     { should be_true }
@@ -19,7 +19,7 @@ describe StoryCommit do
     describe "parse" do
       subject { command.options }
 
-      its(:message) { should == 'msg' }
+      its(:message) { should eq 'msg' }
       its(:all)     { should be_true }
     end
   end
@@ -46,21 +46,21 @@ describe StoryCommit do
 
   describe '#story_id' do
     subject { command.story_id }
-    it { should == '6283185' }
+    it { should eq '62831853' }
   end
 
   describe "command with message" do
     its(:cmd) do
-      should == %(git commit -a -m "msg" -m "[##{command.story_id}]" -z --foo)
+      should eq %(git commit -a -m "msg" -m "[##{command.story_id}]" -z --foo)
     end
 
     describe "when used with branches containing multiple stories" do
       before do
-        command.stub(:story_branch).and_return('6283185-tau-manifesto-3141592')
+        command.stub(:story_branch).and_return('62831853-tau-manifesto-31415926')
       end
       its(:cmd) do
-        delivered_ids = '#6283185 #3141592'
-        should == %(git commit -a -m "msg" -m "[#{delivered_ids}]" -z --foo)
+        delivered_ids = '#62831853 #31415926'
+        should eq %(git commit -a -m "msg" -m "[#{delivered_ids}]" -z --foo)
       end
     end
   end
@@ -68,23 +68,23 @@ describe StoryCommit do
   describe "command with no message" do
     let(:command) { StoryCommit.new(['-a', '-z', '--foo']) }
     its(:cmd) do
-      should == %(git commit -a -m "[##{command.story_id}]" -z --foo)
+      should eq %(git commit -a -m "[##{command.story_id}]" -z --foo)
     end
   end
 
   describe "command with finish flag" do
     let(:command) { StoryCommit.new(['-m', 'msg', '-f']) }
     its(:cmd) do
-      should == %(git commit -m "msg" -m "[Finishes ##{command.story_id}]")
+      should eq %(git commit -m "msg" -m "[Finishes ##{command.story_id}]")
     end
 
     describe "when used with branches containing multiple stories" do
       before do
-        command.stub(:story_branch).and_return('6283185-tau-manifesto-3141592')
+        command.stub(:story_branch).and_return('62831853-tau-manifesto-31415926')
       end
       its(:cmd) do
-        delivered_ids = '#6283185 #3141592'
-        should == %(git commit -m "msg" -m "[Finishes #{delivered_ids}]")
+        delivered_ids = '#62831853 #31415926'
+        should eq %(git commit -m "msg" -m "[Finishes #{delivered_ids}]")
       end
     end
   end
@@ -92,16 +92,16 @@ describe StoryCommit do
   describe "command with deliver flag" do
     let(:command) { StoryCommit.new(['-m', 'msg', '-d']) }
     its(:cmd) do
-      should == %(git commit -m "msg" -m "[Delivers ##{command.story_id}]")
+      should eq %(git commit -m "msg" -m "[Delivers ##{command.story_id}]")
     end
 
     describe "when used with branches containing multiple stories" do
       before do
-        command.stub(:story_branch).and_return('6283185-tau-manifesto-3141592')
+        command.stub(:story_branch).and_return('62831853-tau-manifesto-31415926')
       end
       its(:cmd) do
-        delivered_ids = '#6283185 #3141592'
-        should == %(git commit -m "msg" -m "[Delivers #{delivered_ids}]")
+        delivered_ids = '#62831853 #31415926'
+        should eq %(git commit -m "msg" -m "[Delivers #{delivered_ids}]")
       end
     end
   end
@@ -109,16 +109,16 @@ describe StoryCommit do
   describe "command with no story id" do
     before { command.stub(:story_branch).and_return('tau-manifesto') }
     its(:cmd) do
-      should == %(git commit -a -m "msg" -z --foo)
+      should eq %(git commit -a -m "msg" -z --foo)
     end
   end
 
   describe "command-line command" do
     let(:command) { `bin/git-story-commit -a -m "msg" -z --debug` }
     subject { command }
-    it { should =~ /git commit -a -m/ }
-    it { should =~ /msg/ }
-    it { should =~ /-z/ }
-    it { should_not =~ /--debug/ }
+    it { should match /git commit -a -m/ }
+    it { should match /msg/ }
+    it { should match /-z/ }
+    it { should_not match /--debug/ }
   end
 end

data/spec/commands/story_merge_spec.rb

@@ -3,10 +3,10 @@ require 'spec_helper'
 describe StoryMerge do
 
   let(:command) { StoryMerge.new }
-  before { command.stub(:story_branch).and_return('6283185-tau-manifesto') }
+  before { command.stub(:story_branch).and_return('62831853-tau-manifesto') }
   subject { command }
 
-  its(:cmd) { should =~ /git merge/ }
+  its(:cmd) { should match /git merge/ }
 
   shared_examples "story-merge with known options" do
     subject { command }
@@ -16,24 +16,24 @@ describe StoryMerge do
   end
 
   describe "with no options" do
-    its(:cmd) { should =~ /git checkout master/ }
-    its(:cmd) { should =~ /git merge --no-ff --log #{command.story_branch}/ }
+    its(:cmd) { should match /git checkout master/ }
+    its(:cmd) { should match /git merge --no-ff --log #{command.story_branch}/ }
   end
 
   describe "with a custom development branch" do
     let(:command) { StoryMerge.new(['-d', 'develop']) }
-    its(:cmd) { should =~ /git checkout develop/ }
+    its(:cmd) { should match /git checkout develop/ }
   end
 
   describe "with some unknown options" do
     let(:command) { StoryMerge.new(['-d', 'develop', '-a', '-z', '--foo']) }
     it_should_behave_like "story-merge with known options"
-    its(:cmd) { should =~ /-a -z --foo/ }
+    its(:cmd) { should match /-a -z --foo/ }
   end
 
   describe "command-line command" do
     subject { `bin/git-story-merge --debug -ff -d develop` }
-    it { should =~ /git checkout develop/ }
-    it { should =~ /git merge --no-ff --log -ff/ }
+    it { should match /git checkout develop/ }
+    it { should match /git merge --no-ff --log -ff/ }
   end
 end

data/spec/commands/story_open_spec.rb

@@ -4,8 +4,8 @@ describe StoryOpen do
 
   let(:command) { StoryOpen.new }
   let(:uri) { "https://www.pivotaltracker.com/story/show/#{command.story_id}" }
-  before { command.stub(:story_branch).and_return('6283185-tau-manifesto') }
+  before { command.stub(:story_branch).and_return('62831853-tau-manifesto') }
   subject { command }
 
-  its(:cmd) { should == "open #{uri}" }
+  its(:cmd) { should eq "open #{uri}" }
 end

data/spec/commands/story_pull_request_spec.rb

@@ -3,14 +3,14 @@ require 'spec_helper'
 describe StoryPullRequest do
 
   let(:command) { StoryPullRequest.new }
-  before { command.stub(:story_branch).and_return('6283185-tau-manifesto') }
+  before { command.stub(:story_branch).and_return('62831853-tau-manifesto') }
   before do
     command.stub(:remote_location).
             and_return('https://github.com/mhartl/foo')
   end
   subject { command }
 
-  its(:cmd) { should =~ /git pull-request/ }
+  its(:cmd) { should match /git pull-request/ }
 
   describe 'origin uri parsing' do
     let(:correct_origin) { 'https://github.com/mhartl/foo' }
@@ -32,7 +32,7 @@ describe StoryPullRequest do
 
   describe "command-line command" do
     subject { `bin/git-story-pull-request --debug` }
-    it { should_not =~ /\.git/ }
-    it { should =~ /git pull-request/ }
+    it { should_not match /\.git/ }
+    it { should match /git pull-request/ }
   end
 end

data/spec/spec_helper.rb

@@ -4,4 +4,9 @@ RSpec.configure do |config|
   config.treat_symbols_as_metadata_keys_with_true_values = true
   config.run_all_when_everything_filtered = true
   config.filter_run :focus
+
+  # Disallow the old-style 'object.should' syntax.
+  config.expect_with :rspec do |c|
+    c.syntax = :expect
+  end
 end

metadata

@@ -1,15 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: pivotal-github
 version: !ruby/object:Gem::Version
-  version: 0.8.0
-  prerelease: 
+  version: 0.8.1
 platform: ruby
 authors:
 - Michael Hartl
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-06-04 00:00:00.000000000 Z
+date: 2013-06-06 00:00:00.000000000 Z
 dependencies: []
 description: Add commands for Pivotal Tracker-GitHub integration
 email:
@@ -53,27 +52,26 @@ files:
 - spec/spec_helper.rb
 homepage: https://github.com/mhartl/pivotal-github
 licenses: []
+metadata: {}
 post_install_message: 
 rdoc_options: []
 require_paths:
 - lib
 required_ruby_version: !ruby/object:Gem::Requirement
-  none: false
   requirements:
-  - - ! '>='
+  - - '>='
     - !ruby/object:Gem::Version
       version: '0'
 required_rubygems_version: !ruby/object:Gem::Requirement
-  none: false
   requirements:
-  - - ! '>='
+  - - '>='
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 1.8.25
+rubygems_version: 2.0.3
 signing_key: 
-specification_version: 3
+specification_version: 4
 summary: See the README for full documentation
 test_files:
 - spec/commands/command_spec.rb