blocks|key|416975|text|解决方案是使用Git-Hooks和feature分支。(推荐使用Github-flow+)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|416976|您必须安装此Git-Hook+(将文件复制到本地存储库)：|416977|https://github.com/ktamas77/git_hooks|offset|length|416978|在开始处理特定的Pivotal票证之前，您需要创建一个前缀为Pivotal+Tracker+ID的分支，例如：|416979|git+checkout+1234567_build_new_form|code-block|syntax|javascript|416980|然后像往常一样添加所有更改：|416981|git+commit+-am+'form+added'
git+commit+-am+'styles+added'
git+push+origin|416982|您将看到，git挂钩脚本将自动从feature分支名称中提取Pivotal+Tracker+ID，并将其添加到每个注释的前面。如果需要，您仍然可以手动覆盖它(使用另一个ID)。|416983|通过这种方式，您不必担心为每次提交手动添加Pivotal+ID。它也适用于GUI(比如GIT+It+)，因为这些GUI使用的是标准的GIT库/可执行文件。|416984|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|11|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|14|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|15|8|@]|9|@$F|16|G|17|1|18]]|A|$]]|$1|H|3|I|5|6|7|19|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|1A|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|1B|8|@]|9|@]|A|$]]|$1|Q|3|R|5|L|7|1C|8|@]|9|@]|A|$M|N]]|$1|S|3|T|5|6|7|1D|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1E|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]]|X|$Y|$5|Z|10|11|A|$12|E]]]]

The solution is to use Git-Hooks and feature branches. (The Github-flow is recommended).

You have to install this Git-Hook (copy a file to your local repository):

<a href="https://github.com/ktamas77/git_hooks" rel="noreferrer">https://github.com/ktamas77/git_hooks</a>

Before you start working on a particular Pivotal Ticket, you create a branch prefixed with the Pivotal Tracker ID, for an example:

<pre><code>git checkout 1234567_build_new_form
</code></pre>

then add all your changes as you'd do normally:

<pre><code>git commit -am 'form added'
git commit -am 'styles added'
git push origin
</code></pre>

you'll see, the git hook script will automatically extract the Pivotal Tracker ID from the feature branch name and add it to the front of each comment. You can still manually override it (with another ID) if you want.

In this way you don't have to worry about adding the Pivotal ID manually for every single commit. It also works with GUIS (such as GIT Tower) since these GUIs are using the standard GIT libraries / executables.

blocks|key|417000|text|这是一个基于Tamas解决方案的简单shell版本。它从分支名称的末尾获取ID。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|417001|"my-feature-branch-12345678“=>+"My+commit+mssg+#12345678”。|417002|移动到.git/hooks/prepare-commit-msg并使其成为可执行文件：|417003|#!/bin/bash
if+story_id=`git+branch+%7C+grep+-oP+'%5E\*.*\-\K[0-9]%2B$'`
then
++echo+"[#$story_id]"+>>+"$1"
fi|code-block|syntax|javascript|417004|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|O|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|P|8|@]|9|@]|A|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Here's a simple shell version based on Tamas' solution. It takes the ID from the end of the branch name.

"my-feature-branch-12345678" => "My commit mssg [#12345678]".

Move to .git/hooks/prepare-commit-msg and make it executable:

<pre><code>#!/bin/bash
if story_id=`git branch | grep -oP '^\*.*\-\K[0-9]+$'`
then
 echo "[#$story_id]" &gt;&gt; "$1"
fi
</code></pre>

blocks|key|198900|text|安装'git-pivotal-tracker-integration‘gem，https://github.com/nebhale/git-pivotal-tracker-integration|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|198901|它向git添加了一些命令，比如start和finish，以自动为分支和提交添加跟踪器故事ID的前缀，它还会将提交消息发布到跟踪器。当你调用'git+start‘时，它会拉出master来确保你是最新的，为你创建一个分支，并为你在tracker中开始故事。完成这项工作，然后调用'git+finish‘，它会将你的分支合并回到master和update+tracker中。|198902|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/nebhale/git-pivotal-tracker-integration^0|13|1M|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

Install the 'git-pivotal-tracker-integration' gem, <a href="https://github.com/nebhale/git-pivotal-tracker-integration" rel="nofollow">https://github.com/nebhale/git-pivotal-tracker-integration</a>

It adds commands to git like start and finish to Git to automatically prefix branches and commits with the tracker story ID and it also posts your commit messages to tracker. When you call 'git start' it will pull master to make sure you are up to date, create a branch for you and start the story in tracker for you. Do the work then call 'git finish' and it will merge your branch back in to master and update tracker.

blocks|key|198989|text|我的团队正在使用git_tracker。每个开发人员都必须运行|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|198990|$+git+tracker+init|code-block|syntax|javascript|198991|Pivotal+Tracker上的每个项目一次。然后，他们需要为每个新分支命名一个特殊的约定，并以Pivotal+Tracker故事id作为后缀。例如：|198992|$+git+checkout+-b+the-great-feathure-123456789|198993|其中123456789将是关键跟踪器故事id。|198994|在这里，您将自动让每个提交引用该故事。加分，如果您使用GitHub执行拉请求，您可以要求合并故事的审阅者添加到合并提交中：|198995|[Fixes+#123456789]+...|198996|这样，你永远不需要点击Finish按钮，GitHub将为你做这件事。|198997|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/stevenharman/git_tracker^0|8|B|8|B|0|0|0|0|0|0|0|0|B|6|0^^$0|@$1|2|3|4|5|6|7|14|8|@$9|15|A|16|B|C]]|D|@$9|17|A|18|1|19]]|E|$]]|$1|F|3|G|5|H|7|1A|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|1B|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|1C|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|1D|8|@]|D|@]|E|$]]|$1|Q|3|R|5|6|7|1E|8|@]|D|@]|E|$]]|$1|S|3|T|5|H|7|1F|8|@]|D|@]|E|$I|J]]|$1|U|3|V|5|6|7|1G|8|@$9|1H|A|1I|B|C]]|D|@]|E|$]]|$1|W|3|-4|5|6|7|1J|8|@]|D|@]|E|$]]]|X|$Y|$5|Z|10|11|E|$12|13]]]]

My teams are using <a href="https://github.com/stevenharman/git_tracker" rel="nofollow"><code>git_tracker</code></a>. Each developer must run

<pre><code>$ git tracker init
</code></pre>

once for every project on Pivotal Tracker. Then they need to name each new branch with a special convention, suffixing it with the Pivotal Tracker story id. For instance:

<pre><code>$ git checkout -b the-great-feathure-123456789
</code></pre>

where 123456789 would be the Pivotal Tracker story id.

And here you go, you'll automatically have each commit refering to the story. Bonus point, if you use GitHub to perform pull requests, you can ask reviewers who merge the story to add to the merge commit:

<pre><code>[Fixes #123456789] ...
</code></pre>

This way, you never have to click on the <code>Finish</code> button, GitHub will do it for you.

blocks|key|199042|text|我使用了一个bookmarklet，它还设置了来自故事标题的提交消息。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|199043|[#69609212]+Add+new+Todo|code-block|syntax|javascript|199044|您可以从here获得它|offset|length|199045|entityMap|0|LINK|mutability|MUTABLE|url|http://makandracards.com/makandra/851-bookmarklet-to-generate-a-commit-message-with-pivotal-tracker-story-id-and-title^0|0|0|4|4|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@$I|V|J|W|1|X]]|A|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

I am using a bookmarklet, which also sets the commit message from the story title.

<pre><code>[#69609212] Add new Todo
</code></pre>

You can get it from <a href="http://makandracards.com/makandra/851-bookmarklet-to-generate-a-commit-message-with-pivotal-tracker-story-id-and-title" rel="nofollow">here</a>

blocks|key|417244|text|这是一个能做你想做的事情的gem：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|417245|http://github.com/bogdan/git-storyid|offset|length|417246|它允许从结构精美的菜单中选择一个故事：|417247|[1]+Removing+Billing+Page
[2]+Welcome+Email
[3]+Tag+campaign+insertion+points+and+campaigns+with+an+identifier

Indexes(csv):+3
[campaign-tags+3020407]++[#44116647]+Initial+implementation+of+campaign+tags
+1+file+changed,+101+insertion(%2B),+2+deletions(-)|code-block|syntax|javascript|417248|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|10|0|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@$D|V|E|W|1|X]]|A|$]]|$1|F|3|G|5|6|7|Y|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|Z|8|@]|9|@]|A|$K|L]]|$1|M|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|C]]]]

Here is a gem that does exactly what you want:

<a href="http://github.com/bogdan/git-storyid" rel="nofollow">http://github.com/bogdan/git-storyid</a>

It allows to select a story from a nicely formed menu:

<pre><code>[1] Removing Billing Page
[2] Welcome Email
[3] Tag campaign insertion points and campaigns with an identifier

Indexes(csv): 3
[campaign-tags 3020407] [#44116647] Initial implementation of campaign tags
 1 file changed, 101 insertion(+), 2 deletions(-)
</code></pre>

Pivotal Tracker and Github have great integration: Once it's set up, each commit which is prefixed by the Pivotal Tracker ID will appear under the corresponding Pivotal Ticket automatically, for an example:

<pre><code>git commit -am '[#1234567] my new changes'
git push origin
</code></pre>

will add the comment 'my new changes' automatically to the 1234567 Pivotal Ticket among with the github commit link.

However, it's easy to forget to add the ticket ID each time. How could it be simplified / automated?

How can I automate Pivotal Tracker & Github Integration?

GitHub

Pivotal Tracker和Github有很好的集成:一旦设置，每个以Pivotal Tracker ID为前缀的提交都会自动出现在相应的Pivotal票证下，例如：git commit -am '[#1234567] my new changes'git push origin将使用github提交链接自动将注释...

问如何自动执行Pivotal Tracker和Github集成？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何自动执行Pivotal Tracker和Github集成？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何自动执行Pivotal Tracker和Github集成？
EN