pivotal-github 0.5.6 → 0.6.0

data/README.md

@@ -101,12 +101,18 @@ Because of the way options are chained, passing the option `--ff` to `git story-
 
 #### Options
 
-		Usage: git story-merge [options]
-		    -d, --development BRANCH         development branch (defaults to master)
-		    -h, --help                       this usage guide
+    Usage: git story-merge [options]
+        -d, --development BRANCH         development branch (defaults to master)
+        -h, --help                       this usage guide
 
 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
+
 ### story-open
 
 The `story-open` command (*note*: no `git`) opens the current story in the default browser (OS X–only):
@@ -120,10 +126,11 @@ In order to use the `pivotal-github` gem, you need to configure a [post-receive
 
 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:
 
-    $ git config --global alias.sc story-commit
-    $ git config --global alias.sp story-push    
-    $ git config --global alias.sl story-pull
-    $ git config --global alias.sm story-merge
+    git config --global alias.sc story-commit
+    git config --global alias.sp story-push    
+    git config --global alias.sl story-pull
+    git config --global alias.sm story-merge
+    git config --global alias.spr story-pull-request
 
 A single-developer workflow would then look like this:
 
@@ -163,6 +170,9 @@ Here's the process in detail:
 7. Go the story at Pivotal Tracker and change the **Owner** to Developer #2 (Bob)
 8. Continue working, taking care to branch off of the current story branch if its changes are required to continue
 
+Rather than immediately submitting a pull request, Alice can also continue by branching off the previous story branch, working on a set of related features, and then issue Bob a pull request for the final branch when she reaches a natural stopping place.
+
+
 ### Developer #2 (Bob)
 
 1. Select **Pull Requests** at GitHub and review the pull request diffs

data/bin/git-story-pull-request

@@ -0,0 +1,5 @@
+#!/usr/bin/env ruby
+$LOAD_PATH.unshift File.join(File.dirname(__FILE__), '..', 'lib')
+require 'pivotal-github/story_pull_request'
+
+exit Command.run!(StoryPullRequest, ARGV.dup)

data/lib/pivotal-github/story_pull_request.rb

@@ -0,0 +1,26 @@
+require 'pivotal-github/command'
+
+class StoryPullRequest < Command
+
+  # Returns a command appropriate for executing at the command line
+  # I.e., 'open https://www.pivotaltracker.com/story/show/6283185'
+  def cmd
+    "open #{uri}"
+  end
+
+  def uri
+    "#{origin_uri}/pull/new/#{story_branch}"
+  end
+
+  def run!
+    system cmd
+  end
+
+  private
+
+    # Returns the remote URI for the repository
+    # E.g., https://github.com/mhartl/pivotal-github
+    def origin_uri
+      `git config --get remote.origin.url`.strip.chomp('.git')
+    end  
+end

data/lib/pivotal-github/version.rb

@@ -1,5 +1,5 @@
 module Pivotal
   module Github
-    VERSION = "0.5.6"
+    VERSION = "0.6.0"
   end
 end

data/lib/pivotal-github.rb

@@ -6,3 +6,4 @@ require "pivotal-github/story_push"
 require "pivotal-github/story_pull"
 require "pivotal-github/story_merge"
 require "pivotal-github/story_open"
+require "pivotal-github/story_pull_request"

data/spec/commands/story_pull_request_spec.rb

@@ -0,0 +1,19 @@
+require 'spec_helper'
+
+describe StoryPullRequest do
+
+  let(:command) { StoryPullRequest.new }
+  before { command.stub(:story_branch).and_return('6283185-tau-manifesto') }
+  before do
+    command.stub(:origin_uri).and_return('https://github.com/mhartl/foo')
+  end
+  subject { command }
+
+  its(:cmd) { should == "open #{command.uri}" }
+
+  describe "command-line command" do
+    subject { `bin/git-story-pull-request --debug` }
+    it { should =~ /pull\/new/ }
+    it { should_not =~ /\.git/ }
+  end
+end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: pivotal-github
 version: !ruby/object:Gem::Version
-  version: 0.5.6
+  version: 0.6.0
   prerelease: 
 platform: ruby
 authors:
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-02-12 00:00:00.000000000 Z
+date: 2013-02-13 00:00:00.000000000 Z
 dependencies: []
 description: Add commands for Pivotal Tracker–GitHub integration
 email:
@@ -18,6 +18,7 @@ executables:
 - git-story-commit
 - git-story-merge
 - git-story-pull
+- git-story-pull-request
 - git-story-push
 - story-open
 extensions: []
@@ -32,6 +33,7 @@ files:
 - bin/git-story-commit
 - bin/git-story-merge
 - bin/git-story-pull
+- bin/git-story-pull-request
 - bin/git-story-push
 - bin/story-open
 - lib/pivotal-github.rb
@@ -41,6 +43,7 @@ files:
 - lib/pivotal-github/story_merge.rb
 - lib/pivotal-github/story_open.rb
 - lib/pivotal-github/story_pull.rb
+- lib/pivotal-github/story_pull_request.rb
 - lib/pivotal-github/story_push.rb
 - lib/pivotal-github/version.rb
 - pivotal-github.gemspec
@@ -48,6 +51,7 @@ files:
 - spec/commands/story_commit_spec.rb
 - spec/commands/story_merge_spec.rb
 - spec/commands/story_open_spec.rb
+- spec/commands/story_pull_request_spec.rb
 - spec/commands/story_push_spec.rb
 - spec/options/options_spec.rb
 - spec/options/story_pull_spec.rb
@@ -81,6 +85,7 @@ test_files:
 - spec/commands/story_commit_spec.rb
 - spec/commands/story_merge_spec.rb
 - spec/commands/story_open_spec.rb
+- spec/commands/story_pull_request_spec.rb
 - spec/commands/story_push_spec.rb
 - spec/options/options_spec.rb
 - spec/options/story_pull_spec.rb