git-pivotal-tracker-integration 1.0.0 → 1.1.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 8e313260ee2c9f795dcb3f8bcdf33e3c1fbf18be
-  data.tar.gz: c5ea1e9bc2986243a7a08fcc972749de53a0696b
+  metadata.gz: 7a4c85be1137c7421af33a78659d9b9249533e1a
+  data.tar.gz: 00fd6f4fb8ebc93a351bfa7207d7f0d641f342f8
 SHA512:
-  metadata.gz: 45947162703d4598865b38dfaec580b703ed5db0f17d1a3d6225603645003f721f06c6f06bf5183c3e405f55d91520bb1ece69ff88b0dfe13ef153a307779895
-  data.tar.gz: 0e5afb43bb8e57c391c3f9ebfb2d6ab4065bea60f48578ace2ff8c2c3f6b110e19f3b526b3a72a83068b09d8b716c2849b047a16d3ec235146e7eaffd1497ecb
+  metadata.gz: 3818abcd8243550a5edcd0449c0d1289b3ada53af8a0730522da9d37d9badf782915ab65f32614e83545226ed6d2ceff6762f5978ecb19f5a123f4f01b4a12f2
+  data.tar.gz: 441b962e073172b9035c7e052cdcc2f92878d9dad403c6ca9f5c4d6791fa21f312ef97b88c5e43c421cd6da93bbb831a299f049e30ca93fc08eae189eb1344e2

data/lib/git-pivotal-tracker-integration/start.rb

@@ -58,7 +58,7 @@ class Start < Base
     branch_name = branch_name @story
     create_branch @story, branch_name
     add_commit_hook
-    @story.update(:current_state => "started")
+    start_on_tracker @story
   end
 
   private
@@ -156,7 +156,12 @@ class Start < Base
 
       puts "OK"
     end
+  end
 
+  def start_on_tracker(story)
+    print "Starting story on Pivotal Tracker... "
+    story.update(:current_state => "started")
+    puts "OK"
   end
 
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: git-pivotal-tracker-integration
 version: !ruby/object:Gem::Version
-  version: 1.0.0
+  version: 1.1.0
 platform: ruby
 authors:
 - Ben Hale
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-04-10 00:00:00.000000000 Z
+date: 2013-04-11 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: highline
@@ -66,75 +66,8 @@ dependencies:
     - - '>='
       - !ruby/object:Gem::Version
         version: '0'
-description: "# Git Pivotal Tracker Integration\n\n`git-pivotal-tracker-integration`
-  provides a set of additional Git commands to help developers when working with [Pivotal
-  Tracker][pivotal-tracker].\n\n[pivotal-tracker]: http://www.pivotaltracker.com\n\n\n##
-  Installation\n`git-pivotal-tracker-integration` requires at least **Ruby 2.0.0**
-  and **Git 1.8.2.1** in order to run.  In order to install it, do the following:\n\n```plain\n$
-  gem install git-pivotal-tracker-integration\n```\n\n\n## Usage\n`git-pivotal-tracker-integration`
-  is intended to be a very lightweight tool, meaning that it won't affect your day
-  to day workflow very much.  To be more specific, it is intended to automate branch
-  creation and destruction as well as story state changes, but will not affect when
-  you commit, when development branches are pushed to origin, etc.  The typical workflow
-  looks something like the following:\n\n```plain\n$ git start       # Creates branch
-  and starts story\n$ git commit ...\n$ git commit ...  # Your existing development
-  process\n$ git commit ...\n$ git finish      # Merges and destroys branch, pushes
-  to origin, and finishes story\n```\n\n\n## Configuration\n\n### Git Client\nIn order
-  to use `git-pivotal-tracker-integration`, two Git client configuration properties
-  must be set.  If these properties have not been set, you will be prompted for them
-  and your Git configuration will be updated.\n\n| Name | Description\n| ---- | -----------\n|
-  `pivotal.api-token` | Your Pivotal Tracker API Token.  This can be found in [your
-  profile][profile] and should be set globally.\n| `pivotal.project-id` | The Pivotal
-  Tracker project id for the repository your are working in.  This can be found in
-  the project's URL and should be set.\n\n[profile]: https://www.pivotaltracker.com/profile\n\n\n###
-  Git Server\nIn order to take advantage of automatic issue completion, the [Pivotal
-  Tracker Source Code Integration][integration] must be enabled.  If you are using
-  GitHub, this integration is easy to enable by navgating to your project's 'Service
-  Hooks' settings and configuring it with the proper credentials.\n\n[integration]:
-  https://www.pivotaltracker.com/help/integrations?version=v3#scm\n\n\n## Commands\n\n###
-  `git start [ type | issue ]`\nThis command starts a story by creating a Git branch
-  and changing the story's state to `started`.  This command can be run in three ways.
-  \ First it can be run specifying the issue that you want to start.\n\n```plain\n$
-  git start 12345678\n```\n\nThe second way to run the command is by specyifying the
-  type of story that you would like to start.  In this case it will then offer you
-  the first five stories (based on the backlog's order) of that type to choose from.\n\n```plain\n$
-  git start feature\n\n1. Lorem ipsum dolor sit amet, consectetur adipiscing elit\n2.
-  Pellentesque sit amet ante eu tortor rutrum pharetra\n3. Ut at purus dolor, vel
-  ultricies metus\n4. Duis egestas elit et leo ultrices non fringilla ante facilisis\n5.
-  Ut ut nunc neque, quis auctor mauris\nChoose story to start:\n```\n\nFinally the
-  command can be run without specifying anything.  In this case, it will then offer
-  the first five stories (based on the backlog's order) of any type to choose from.\n\n```plain\n$
-  git start\n\n1. FEATURE Donec convallis leo mi, dictum ornare sem\n2. CHORE   Sed
-  et magna lectus, sed auctor purus\n3. FEATURE In a nunc et enim tincidunt interdum
-  vitae et risus\n4. FEATURE Fusce facilisis varius lorem, at tristique sem faucibus
-  in\n5. BUG     Donec iaculis ante neque, ut tempus augue\nChoose story to start:\n```\n\nOnce
-  a story has been selected by one of the three methods, the command then prompts
-  for the name of the branch to create.\n\n```plain\n$ git start 12345678\n        Title:
-  Lorem ipsum dolor sit amet, consectetur adipiscing elitattributes\n  Description:
-  Ut consequat sapien ut erat volutpat egestas. Integer venenatis lacinia facilisis.\n\nEnter
-  branch name (12345678-<branch-name>):\n```\n\nThe value entered here will be prepended
-  with the story id such that the branch name is `<project-id>-<branch-name>`.  This
-  branch is then created and checked out.\n\nIf it doesn't exist already, a `prepare-commit-msg`
-  commit hook is added to your repository.  This commit hook augments the existing
-  commit messsage pattern by appending the story id to the message automatically.\n\n```plain\n\n\n[#12345678]\n#
-  Please enter the commit message for your changes. Lines starting\n# with '#' will
-  be ignored, and an empty message aborts the commit.\n# On branch 12345678-lorem-ipsum\n#
-  Changes to be committed:\n#   (use \"git reset HEAD <file>...\" to unstage)\n#\n#\tnew
-  file:   dolor.txt\n#\n```\n\n### `git finish`\nThis command finishes a story by
-  merging and cleaning up its branch and then pushing the changes to a remote server.
-  \ This command can only be run one way.\n\n```plain\n$ git finish\nChecking for
-  trivial merge from 12345678-lorem-ipsum to master... OK\nMerging 12345678-lorem-ipsum
-  to master... OK\nDeleting 12345678-lorem-ipsum... OK\nPushing to origin... OK\n```\n\nThe
-  command checks that it will be able to do a trivial merge from the development branch
-  to the target branch before it does anything.  The check has the following constraints\n\n1.
-  \ The local repository must be up to date with the remote repository (e.g. `origin`)\n2.
-  \ The local merge target branch (e.g. `master`) must be up to date with the remote
-  merge target branch (e.g. `origin/master`)\n3.  The common ancestor (i.e. the branch
-  point) of the development branch (e.g. `12345678-lorem-ipsum`) must be tip of the
-  local merge target branch (e.g. `master`)\n\nIf all of these conditions are met,
-  the development branch will be merged into the target branch with a message of:\n\n```plain\nMerge
-  12345678-lorem-ipsum to master\n\n[Completes #12345678]\n```\n\nAfter merging, the
-  development branch is deleted and the changes are pushed to the remote repository.\n"
+description: Provides a set of additional Git commands to help developers when working
+  with Pivotal Tracker
 email: nebhale@nebhale.com
 executables:
 - git-finish