pivotal-integration 1.6.0.1

checksums.yaml

@@ -0,0 +1,15 @@
+---
+!binary "U0hBMQ==":
+  metadata.gz: !binary |-
+    ODY3YjFhNGFjYjYxMjdhYmU1Zjc3Mzg0YjVhZTk0NjQwYjZhYWU0Zg==
+  data.tar.gz: !binary |-
+    Mjk2ODZhNjI5NGY1OTk4ZGI4NTcyNzYyZGM1ZmY2OWM2NjA4OGE3Yw==
+SHA512:
+  metadata.gz: !binary |-
+    YzM2NTFmNDNmMjY1MjFmOTBjZmFhYWU0ODdlMjZjZjZmMmFmOTA1MmM2N2Vj
+    NTU5ZWMyZjA4NGIxMjRmYTJkMGNiZjhlMDAyMzRhZjQ3NDRiYzVmOGIwOTAy
+    MDM1ODU0ZTZjZjUwNTFhOWU1MjJmMGVkOGM4ZWExODM4NzVhYjQ=
+  data.tar.gz: !binary |-
+    ZTgwZTE5YjA5MjNjN2JhYmY4MDI2ZDI0OTdkZjE3MmJjNzE1YTg0ZjIwZmIy
+    NGM1ZjY3YzZhNmQ0YjQwYzAzMjFkYmM0MzFiYzg2MjNkZmNlOGI4N2JlMDc0
+    OGY5OGE1NjYzNWI0Mjg1NzAxYmU5YWE2YTIzOTdiZmFhN2MxNTg=

data/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

data/NOTICE

@@ -0,0 +1,2 @@
+   Git Pivotal Tracker Integration
+   Copyright 2013 the original author or authors.

data/README.md

@@ -0,0 +1,331 @@
+# Git Pivotal Tracker Integration
+[![Build Status](https://travis-ci.org/nebhale/git-pivotal-tracker-integration.png?branch=master)](https://travis-ci.org/nebhale/git-pivotal-tracker-integration)
+[![Gem Version](https://badge.fury.io/rb/git-pivotal-tracker-integration.png)](http://badge.fury.io/rb/git-pivotal-tracker-integration)
+[![Dependency Status](https://gemnasium.com/nebhale/git-pivotal-tracker-integration.png)](http://gemnasium.com/nebhale/git-pivotal-tracker-integration)
+[![Code Climate](https://codeclimate.com/github/nebhale/git-pivotal-tracker-integration.png)](https://codeclimate.com/github/nebhale/git-pivotal-tracker-integration)
+
+
+`pivotal-integration` provides a set of additional Git commands to help developers when working with [Pivotal Tracker][pivotal-tracker].
+
+[pivotal-tracker]: http://www.pivotaltracker.com
+
+
+## Installation
+`pivotal-integration` requires at least **Ruby 1.8.7** and **Git 1.8.2.1** in order to run.  It is tested against Rubies _1.8.7_, _1.9.3_, and _2.0.0_.  In order to install it, do the following:
+
+```plain
+$ gem install pivotal-integration
+```
+
+
+## Usage
+`pivotal-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:
+
+```plain
+$ pivotal start       # Creates branch and starts story
+$ git commit ...
+$ git commit ...      # Your existing development process
+$ git commit ...
+$ pivotal finish      # Merges and destroys branch, pushes to origin, and finishes story
+```
+
+
+## Configuration
+
+### Git Client
+In order to use `pivotal-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.
+
+| Name | Description
+| ---- | -----------
+| `pivotal.api-token` | Your Pivotal Tracker API Token.  This can be found in [your profile][profile] and should be set globally.
+| `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.
+
+[profile]: https://www.pivotaltracker.com/profile
+
+
+### Git Server
+In 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.
+
+[integration]: https://www.pivotaltracker.com/help/integrations?version=v3#scm
+
+
+## Commands
+
+### `pivotal start [new] [ type | story-id ]`
+This command starts a story by creating a Git branch and changing the story's state to `started`.  This command can be run in four ways.  First it can be run specifying the id of the story that you want to start.
+
+```plain
+$ pivotal start 12345678
+```
+
+The second way to run the command is by specifying 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.
+
+```plain
+$ pivotal start feature
+
+1. Lorem ipsum dolor sit amet, consectetur adipiscing elit
+2. Pellentesque sit amet ante eu tortor rutrum pharetra
+3. Ut at purus dolor, vel ultricies metus
+4. Duis egestas elit et leo ultrices non fringilla ante facilisis
+5. Ut ut nunc neque, quis auctor mauris
+Choose story to start:
+```
+
+The third way to run the command lets you create a new story straight from the command line. You can specify which type of story you'd like to create in the command, or you will be prompted to choose. The story name and estimate is also specified. The new story will then be assigned and started.
+
+```plain
+$ pivotal start new
+1. Feature
+2. Bug
+3. Chore
+4. Release
+What type of story do you want to create: 
+Provide a name for the new story:
+Choose an estimation for this story [0, 1, 2, 3, enter for none]: 
+```
+
+Finally 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.
+
+```plain
+$ pivotal start
+
+1. FEATURE Donec convallis leo mi, dictum ornare sem
+2. CHORE   Sed et magna lectus, sed auctor purus
+3. FEATURE In a nunc et enim tincidunt interdum vitae et risus
+4. FEATURE Fusce facilisis varius lorem, at tristique sem faucibus in
+5. BUG     Donec iaculis ante neque, ut tempus augue
+Choose story to start:
+```
+
+Once a story has been selected by one of the methods, the command then prompts for the name of the branch to create.
+
+```plain
+$ pivotal start 12345678
+        Title: Lorem ipsum dolor sit amet, consectetur adipiscing elitattributes
+  Description: Ut consequat sapien ut erat volutpat egestas. Integer venenatis lacinia facilisis.
+
+Enter branch name (12345678-<branch-name>):
+```
+
+The value entered here will be prepended with the story id such that the branch name is `<story-id>-<branch-name>`.  This branch is then created and checked out.
+
+If 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.
+
+```plain
+
+[#12345678]
+# Please enter the commit message for your changes. Lines starting
+# with '#' will be ignored, and an empty message aborts the commit.
+# On branch 12345678-lorem-ipsum
+# Changes to be committed:
+#   (use "git reset HEAD <file>..." to unstage)
+#
+#	new file:   dolor.txt
+#
+```
+
+### `pivotal finish [--no-complete] [--pull-request] [--no-merge]`
+This command finishes a story. There are two workflows that can be used for finishing (pull requests and merging).
+
+#### Pull Request Workflow
+The pull request workflow can be accessed by specifying the `--pull-request` option, or by setting `pivotal.finish-mode` to `pull_request` in your git config. When using the PR workflow, when finishing a story, the branch will be pushed to the `origin` remote, and PR will be started (either launched in a web browser, or through the console using [hub](https://github.com/github/hub)). The behaviour can be specified by setting `pivotal.pull-request-editor` to `web` or `hub` in your git config.
+
+In both cases, the story will also be updated to mark its status as Finished.
+
+```plain
+$ pivotal finish --pull-request
+Pushing to origin... OK
+Changing state to finished
+```
+
+#### Merge Workflow
+This command finishes a story by merging and cleaning up its branch and then pushing the changes to a remote server.  This command can be run in two ways.  First it can be run without the `--no-complete` option.
+
+```plain
+$ pivotal finish
+Checking for trivial merge from 12345678-lorem-ipsum to master... OK
+Merging 12345678-lorem-ipsum to master... OK
+Deleting 12345678-lorem-ipsum... OK
+Pushing to origin... OK
+```
+
+The 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
+
+1.  The local repository must be up to date with the remote repository (e.g. `origin`)
+2.  The local merge target branch (e.g. `master`) must be up to date with the remote merge target branch (e.g. `origin/master`)
+3.  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`)
+
+If all of these conditions are met, the development branch will be merged into the target branch with a message of:
+
+```plain
+Merge 12345678-lorem-ipsum to master
+
+[Completes #12345678]
+```
+
+The second way is with the `--no-complete` option specified. In this case `finish` performs the same actions except the `Completes`... statement in the commit message will be supressed.
+
+```plain
+Merge 12345678-lorem-ipsum to master
+
+[#12345678]
+```
+
+After merging, the development branch is deleted and the changes are pushed to the remote repository.
+
+### `pivotal release [story-id]`
+This command creates a release for a story.  It does this by updating the version string in the project and creating a tag.  This command can be run in two ways.  First it can be run specifying the release that you want to create.
+
+```plain
+$ pivotal release 12345678
+```
+The other way the command can be run without specifying anything.  In this case, it will select the first release story (based on the backlog's order).
+
+```plain
+$ pivotal release
+      Title: Lorem ipsum dolor sit amet, consectetur adipiscing elitattributes
+```
+
+Once a story has been selected by one of the two methods, the command then prompts for the release version and next development version.
+
+```plain
+$ pivotal release
+      Title: Lorem ipsum dolor sit amet, consectetur adipiscing elitattributes
+
+Enter release version (current: 1.0.0.BUILD-SNAPSHOT): 1.0.0.M1
+Enter next development version (current: 1.0.0.BUILD-SNAPSHOT): 1.1.0.BUILD-SNAPSHOT
+Creating tag v1.0.0.M1... OK
+Pushing to origin... OK
+```
+
+Once these have been entered, the version string for the current project is updated to the release version and a tag is created.  Then the version string for the current project is updated to the next development version and a new commit along the original branch is created.  Finally the tag and changes are pushed to the remote sever.
+
+Version update is currently supported for the following kinds of projects.  If you do not see a project type that you would like supported, please open an issue or submit a pull request.
+
+### `pivotal new [type] [name]` 
+This command lets you create a new story in Pivotal Tracker directly from the command line. The story type and name can be provided as command line options or from prompts. Creating a story in this way adds it to the Icebox, and does not assign or start the story (contrasted to `pivotal start new`).
+
+```plain
+$ pivotal new feature "Create a blog"
+```
+
+```plain
+pivotal new
+1. Feature
+2. Bug
+3. Chore
+4. Release
+What type of story do you want to create: 
+Provide a name for the new story: 
+```
+
+### `pivotal info`
+This command gives you an output of info from the current story (including description, notes, etc.).
+
+```plain
+$ pivotal info
+         ID: 123456
+    Project: My Project
+      Title: Create a blog
+       Type: Feature
+      State: Started
+   Estimate: 3
+     Note 1: How many posts do we want to limit the blog to?
+```
+
+### `pivotal estimate [points]`
+This command lets you set or change the estimate for the current story. This command can be run in two ways. First it can be run by specifying the score you want to assign.
+
+```plain
+$ pivotal estimate 3
+```
+
+The second way is to run the command with specifying anything. In this case, the current estimate will be shown, as well as all the possible values (as set up for the project in Pivotal Tracker). In this mode, you can also choose to remove the estimate by leaving the score prompt blank.
+
+```plain
+$ pivotal estimate
+Story is currently estimated 3.
+Choose an estimation for this story [0, 1, 2, 3, enter for none]:
+```
+
+### `pivotal switch ID`
+This command lets you switch the active Pivotal Tracker story to a different one.
+
+```plain
+$ pivotal switch 12345678
+```
+
+### `pivotal assign [username]`
+This command assigns current story to another member of Pivotal Tracker project.  This command can be run in two ways.  First it can be run with specific username of project's member. If username consists of more than one world use braces as in example.
+
+```plain
+$ pivotal assign 'Mark Twain'
+```
+
+The other way the command can be run without specifying anything.  In this case, you will be able to choose from all project members.
+
+```plain
+$ pivotal assign
+
+1. Mark Twain
+2. Edgar Alan Poe
+Choose an user from above list:
+```
+
+### `pivotal label [mode] label1 ... labeln`
+This command manages story labels, there are four modes you can use:
+* add - appends new labels to story
+* once - appends new labels to story and removes it's occurences from every other story in project
+* remove - removes labels from story
+* list - lists labels attached to current story
+
+```plain
+$ pivotal label list
+```
+
+You have to specify mode and at least on label if you are using add, once or remove modes.
+
+```plain
+$ pivotal label add on_qa
+```
+
+### `pivotal mark [state]`
+This command marks current story with specified state. You can add desired state as follows:
+
+```plain
+$ pivotal mark finished
+```
+
+The other way the command can be run without specifying anything.  In this case, you will be able to choose from all possible states.
+
+```plain
+$ pivotal mark
+
+1. unstarted
+2. started
+3. finished
+4. delivered
+5. rejected
+6. accepted
+Choose story state from above list:
+```
+
+### `pivotal comment TEXT`
+This command allows you to add a comment (note) to the current story. The comment text must be given with the command.
+
+```plain
+$ pivotal comment "Good idea!"
+```
+
+### `pivotal open [project]`
+This command lets you open the current story or project in a web browser (this functionality is provided by [launchy](https://github.com/copiousfreetime/launchy) and may not work in all environments). There are two ways the command can be run in. First, if you want to open the current story directly.
+
+```plain
+$ pivotal open
+```
+
+Second, if you want to open the entire project
+
+```plain
+$ pivotal open project
+```

data/bin/pivotal

@@ -0,0 +1,81 @@
+#!/usr/bin/env ruby -U
+# Git Pivotal Tracker Integration
+# Copyright (c) 2013 the original author or authors.
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+#      http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+require 'active_support'
+require 'active_support/core_ext/string'
+
+Dir.glob(File.expand_path("../../lib/pivotal-integration/command/*.rb", __FILE__)).each do |file|
+  next if %w(base.rb command.rb configuration.rb).include?(File.basename(file))
+  require file
+end
+
+COMMANDS = ObjectSpace.each_object(Class).select { |klass| klass < PivotalIntegration::Command::Base }
+COMMAND_NAMES = COMMANDS.map{|c|c.name.demodulize.downcase}
+MAX_COMMAND_LEN = COMMAND_NAMES.map(&:length).max
+
+def print_command_help(commands)
+  commands.each do |command|
+    puts "  %-#{MAX_COMMAND_LEN}s   %s" % [command.name.demodulize.downcase, command.description]
+  end
+end
+
+def show_help
+  puts "Usage: git pivotal [--help] <command> [<args>]"
+  puts
+
+  main_commands = COMMANDS.select{ |c| %w(start finish new).include? c.name.demodulize.downcase }
+  secondary_commands = COMMANDS - main_commands
+
+  puts "Main Commands"
+  print_command_help(main_commands.sort_by{ |c| %w(new start finish).index(c.name.demodulize.downcase) })
+
+  puts
+  puts "Secondary Commands:"
+  print_command_help(secondary_commands.sort_by(&:name))
+end
+
+begin
+  options = {}
+  optparse = OptionParser.new do |opts|
+    opts.on('-h', '--help') do
+      show_help
+      exit
+    end
+
+    opts.on('-S', '--story ID') do |id|
+      options[:story_id] = id
+    end
+  end
+  optparse.parse!
+
+  if COMMAND_NAMES.include?(ARGV.first.try(:downcase))
+    command = ARGV.shift
+    command_class = PivotalIntegration::Command.const_get(command.classify)
+    command_class.new(options).run(*ARGV)
+
+  elsif ARGV.empty?
+    show_help
+
+  else
+    abort "Invalid command #{ARGV.first}."
+  end
+
+rescue Interrupt
+  puts
+  puts "Operation cancelled."
+  exit
+end
+#

data/lib/pivotal-integration/command/assign.rb

@@ -0,0 +1,50 @@
+# Git Pivotal Tracker Integration
+# Copyright (c) 2013 the original author or authors.
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+#      http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+require_relative 'base'
+require 'pivotal-tracker'
+
+# The class that encapsulates assigning current Pivotal Tracker Story to a user
+class PivotalIntegration::Command::Assign < PivotalIntegration::Command::Base
+  desc "Assign the current story to a user"
+
+  # Assigns story to user.
+  # @return [void]
+  def run(*arguments)
+    username = arguments.first
+
+    if username.nil? or !memberships.include?(username)
+      username = choose_user
+    end
+
+    PivotalIntegration::Util::Story.assign(story, username)
+  end
+
+  private
+
+  def choose_user
+    choose do |menu|
+      menu.prompt = 'Choose an user from above list: '
+
+      memberships.each do |membership|
+        menu.choice(membership)
+      end
+    end
+  end
+
+  def memberships
+    @project.memberships.all.map(&:name)
+  end
+end