pivotal-github 0.5.4 → 0.5.5
Sign up to get free protection for your applications and to get access to all the features.
- data/README.md +3 -5
- data/lib/pivotal-github/version.rb +1 -1
- metadata +2 -2
data/README.md
CHANGED
@@ -123,7 +123,7 @@ The `story-open` command (*note*: no `git`) opens the current story in the defau
|
|
123
123
|
|
124
124
|
## Configuration
|
125
125
|
|
126
|
-
In order to use the `pivotal-github` gem, you need to configure a [post-receive hook for Pivotal Tracker at GitHub](https://www.pivotaltracker.com/help/api?version=v3#github_hooks) for your repository. (To find your Pivotal Tracker API token, go to your user profile and scroll to the bottom.)
|
126
|
+
In order to use the `pivotal-github` gem, you need to configure a [post-receive hook for Pivotal Tracker at GitHub](https://www.pivotaltracker.com/help/api?version=v3#github_hooks) for your repository. (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.
|
127
127
|
|
128
128
|
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:
|
129
129
|
|
@@ -167,7 +167,7 @@ Here's the process in detail:
|
|
167
167
|
4. Rebase against `master` using `git story-pull` 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))
|
168
168
|
4. Push up with `git push`
|
169
169
|
6. At the GitHub page for the repo, select **Branches** and submit a pull request
|
170
|
-
7.
|
170
|
+
7. Go the story at Pivotal Tracker and change the **Owner** to Developer #2 (Bob)
|
171
171
|
8. Continue working, taking care to branch off of the current story branch if its changes are required to continue
|
172
172
|
|
173
173
|
### Developer #2 (Bob)
|
@@ -175,9 +175,7 @@ Here's the process in detail:
|
|
175
175
|
1. Select **Pull Requests** at GitHub and review the pull request diffs
|
176
176
|
2. If acceptable, merge the branch by clicking on the button at GitHub
|
177
177
|
3. If not acceptable, manually change the state at Pivotal Tracker to **Rejected** and leave a note (at GitHub or at Pivotal Tracker) indicating the reason
|
178
|
-
4.
|
179
|
-
|
180
|
-
Note that the commits will appear on the story as soon as Alice creates a remote branch (and as she pushes to it), but it won't be marked **Finished** or **Delivered** until Bob merges the pull request into `master`.
|
178
|
+
4. If the branch can't be automatically merged, mark the story as **Rejected** and change the **Owner** back to Alice
|
181
179
|
|
182
180
|
## Merge conflicts
|
183
181
|
|
metadata
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: pivotal-github
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.5.
|
4
|
+
version: 0.5.5
|
5
5
|
prerelease:
|
6
6
|
platform: ruby
|
7
7
|
authors:
|
@@ -9,7 +9,7 @@ authors:
|
|
9
9
|
autorequire:
|
10
10
|
bindir: bin
|
11
11
|
cert_chain: []
|
12
|
-
date: 2013-02-
|
12
|
+
date: 2013-02-12 00:00:00.000000000 Z
|
13
13
|
dependencies: []
|
14
14
|
description: Add commands for Pivotal Tracker–GitHub integration
|
15
15
|
email:
|