git-pivotal-tracker-integration 1.0.0 → 1.1.0
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/lib/git-pivotal-tracker-integration/start.rb +6 -1
- metadata +4 -71
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 7a4c85be1137c7421af33a78659d9b9249533e1a
|
4
|
+
data.tar.gz: 00fd6f4fb8ebc93a351bfa7207d7f0d641f342f8
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 3818abcd8243550a5edcd0449c0d1289b3ada53af8a0730522da9d37d9badf782915ab65f32614e83545226ed6d2ceff6762f5978ecb19f5a123f4f01b4a12f2
|
7
|
+
data.tar.gz: 441b962e073172b9035c7e052cdcc2f92878d9dad403c6ca9f5c4d6791fa21f312ef97b88c5e43c421cd6da93bbb831a299f049e30ca93fc08eae189eb1344e2
|
@@ -58,7 +58,7 @@ class Start < Base
|
|
58
58
|
branch_name = branch_name @story
|
59
59
|
create_branch @story, branch_name
|
60
60
|
add_commit_hook
|
61
|
-
@story
|
61
|
+
start_on_tracker @story
|
62
62
|
end
|
63
63
|
|
64
64
|
private
|
@@ -156,7 +156,12 @@ class Start < Base
|
|
156
156
|
|
157
157
|
puts "OK"
|
158
158
|
end
|
159
|
+
end
|
159
160
|
|
161
|
+
def start_on_tracker(story)
|
162
|
+
print "Starting story on Pivotal Tracker... "
|
163
|
+
story.update(:current_state => "started")
|
164
|
+
puts "OK"
|
160
165
|
end
|
161
166
|
|
162
167
|
end
|
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: git-pivotal-tracker-integration
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 1.
|
4
|
+
version: 1.1.0
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Ben Hale
|
8
8
|
autorequire:
|
9
9
|
bindir: bin
|
10
10
|
cert_chain: []
|
11
|
-
date: 2013-04-
|
11
|
+
date: 2013-04-11 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
name: highline
|
@@ -66,75 +66,8 @@ dependencies:
|
|
66
66
|
- - '>='
|
67
67
|
- !ruby/object:Gem::Version
|
68
68
|
version: '0'
|
69
|
-
description:
|
70
|
-
|
71
|
-
Tracker][pivotal-tracker].\n\n[pivotal-tracker]: http://www.pivotaltracker.com\n\n\n##
|
72
|
-
Installation\n`git-pivotal-tracker-integration` requires at least **Ruby 2.0.0**
|
73
|
-
and **Git 1.8.2.1** in order to run. In order to install it, do the following:\n\n```plain\n$
|
74
|
-
gem install git-pivotal-tracker-integration\n```\n\n\n## Usage\n`git-pivotal-tracker-integration`
|
75
|
-
is intended to be a very lightweight tool, meaning that it won't affect your day
|
76
|
-
to day workflow very much. To be more specific, it is intended to automate branch
|
77
|
-
creation and destruction as well as story state changes, but will not affect when
|
78
|
-
you commit, when development branches are pushed to origin, etc. The typical workflow
|
79
|
-
looks something like the following:\n\n```plain\n$ git start # Creates branch
|
80
|
-
and starts story\n$ git commit ...\n$ git commit ... # Your existing development
|
81
|
-
process\n$ git commit ...\n$ git finish # Merges and destroys branch, pushes
|
82
|
-
to origin, and finishes story\n```\n\n\n## Configuration\n\n### Git Client\nIn order
|
83
|
-
to use `git-pivotal-tracker-integration`, two Git client configuration properties
|
84
|
-
must be set. If these properties have not been set, you will be prompted for them
|
85
|
-
and your Git configuration will be updated.\n\n| Name | Description\n| ---- | -----------\n|
|
86
|
-
`pivotal.api-token` | Your Pivotal Tracker API Token. This can be found in [your
|
87
|
-
profile][profile] and should be set globally.\n| `pivotal.project-id` | The Pivotal
|
88
|
-
Tracker project id for the repository your are working in. This can be found in
|
89
|
-
the project's URL and should be set.\n\n[profile]: https://www.pivotaltracker.com/profile\n\n\n###
|
90
|
-
Git Server\nIn order to take advantage of automatic issue completion, the [Pivotal
|
91
|
-
Tracker Source Code Integration][integration] must be enabled. If you are using
|
92
|
-
GitHub, this integration is easy to enable by navgating to your project's 'Service
|
93
|
-
Hooks' settings and configuring it with the proper credentials.\n\n[integration]:
|
94
|
-
https://www.pivotaltracker.com/help/integrations?version=v3#scm\n\n\n## Commands\n\n###
|
95
|
-
`git start [ type | issue ]`\nThis command starts a story by creating a Git branch
|
96
|
-
and changing the story's state to `started`. This command can be run in three ways.
|
97
|
-
\ First it can be run specifying the issue that you want to start.\n\n```plain\n$
|
98
|
-
git start 12345678\n```\n\nThe second way to run the command is by specyifying the
|
99
|
-
type of story that you would like to start. In this case it will then offer you
|
100
|
-
the first five stories (based on the backlog's order) of that type to choose from.\n\n```plain\n$
|
101
|
-
git start feature\n\n1. Lorem ipsum dolor sit amet, consectetur adipiscing elit\n2.
|
102
|
-
Pellentesque sit amet ante eu tortor rutrum pharetra\n3. Ut at purus dolor, vel
|
103
|
-
ultricies metus\n4. Duis egestas elit et leo ultrices non fringilla ante facilisis\n5.
|
104
|
-
Ut ut nunc neque, quis auctor mauris\nChoose story to start:\n```\n\nFinally the
|
105
|
-
command can be run without specifying anything. In this case, it will then offer
|
106
|
-
the first five stories (based on the backlog's order) of any type to choose from.\n\n```plain\n$
|
107
|
-
git start\n\n1. FEATURE Donec convallis leo mi, dictum ornare sem\n2. CHORE Sed
|
108
|
-
et magna lectus, sed auctor purus\n3. FEATURE In a nunc et enim tincidunt interdum
|
109
|
-
vitae et risus\n4. FEATURE Fusce facilisis varius lorem, at tristique sem faucibus
|
110
|
-
in\n5. BUG Donec iaculis ante neque, ut tempus augue\nChoose story to start:\n```\n\nOnce
|
111
|
-
a story has been selected by one of the three methods, the command then prompts
|
112
|
-
for the name of the branch to create.\n\n```plain\n$ git start 12345678\n Title:
|
113
|
-
Lorem ipsum dolor sit amet, consectetur adipiscing elitattributes\n Description:
|
114
|
-
Ut consequat sapien ut erat volutpat egestas. Integer venenatis lacinia facilisis.\n\nEnter
|
115
|
-
branch name (12345678-<branch-name>):\n```\n\nThe value entered here will be prepended
|
116
|
-
with the story id such that the branch name is `<project-id>-<branch-name>`. This
|
117
|
-
branch is then created and checked out.\n\nIf it doesn't exist already, a `prepare-commit-msg`
|
118
|
-
commit hook is added to your repository. This commit hook augments the existing
|
119
|
-
commit messsage pattern by appending the story id to the message automatically.\n\n```plain\n\n\n[#12345678]\n#
|
120
|
-
Please enter the commit message for your changes. Lines starting\n# with '#' will
|
121
|
-
be ignored, and an empty message aborts the commit.\n# On branch 12345678-lorem-ipsum\n#
|
122
|
-
Changes to be committed:\n# (use \"git reset HEAD <file>...\" to unstage)\n#\n#\tnew
|
123
|
-
file: dolor.txt\n#\n```\n\n### `git finish`\nThis command finishes a story by
|
124
|
-
merging and cleaning up its branch and then pushing the changes to a remote server.
|
125
|
-
\ This command can only be run one way.\n\n```plain\n$ git finish\nChecking for
|
126
|
-
trivial merge from 12345678-lorem-ipsum to master... OK\nMerging 12345678-lorem-ipsum
|
127
|
-
to master... OK\nDeleting 12345678-lorem-ipsum... OK\nPushing to origin... OK\n```\n\nThe
|
128
|
-
command checks that it will be able to do a trivial merge from the development branch
|
129
|
-
to the target branch before it does anything. The check has the following constraints\n\n1.
|
130
|
-
\ The local repository must be up to date with the remote repository (e.g. `origin`)\n2.
|
131
|
-
\ The local merge target branch (e.g. `master`) must be up to date with the remote
|
132
|
-
merge target branch (e.g. `origin/master`)\n3. The common ancestor (i.e. the branch
|
133
|
-
point) of the development branch (e.g. `12345678-lorem-ipsum`) must be tip of the
|
134
|
-
local merge target branch (e.g. `master`)\n\nIf all of these conditions are met,
|
135
|
-
the development branch will be merged into the target branch with a message of:\n\n```plain\nMerge
|
136
|
-
12345678-lorem-ipsum to master\n\n[Completes #12345678]\n```\n\nAfter merging, the
|
137
|
-
development branch is deleted and the changes are pushed to the remote repository.\n"
|
69
|
+
description: Provides a set of additional Git commands to help developers when working
|
70
|
+
with Pivotal Tracker
|
138
71
|
email: nebhale@nebhale.com
|
139
72
|
executables:
|
140
73
|
- git-finish
|