您使用Mercurial协调Pivotal Tracker的工作流程是什么?

前端之家收集整理的这篇文章主要介绍了您使用Mercurial协调Pivotal Tracker的工作流程是什么?前端之家小编觉得挺不错的,现在分享给大家,也给大家做个参考。
我想将 Pivotal Tracker用于新项目,但我不知道如何将它与Mercurial一起使用,以便轻松地从一个工具转到另一个工具.

您使用什么工作流程将Pivotal Tracker中的用户故事/功能与您的DVCS(Mercurial / Git)相关联?

提前感谢您的建议.

解决方法

如果有人仍在寻找答案,则存在一种服务,允许mercurial用户在其提交消息中使用[#story_id finished]等语法连接到关键跟踪器. Bitbucket也允许这种集成.

链接https://bitbucket.org/proppy/hgpivotal/src/tip/hgpivotal.py

07001:

The minimum commit message string that will allow Tracker to associate
a source_commits POST with a story and create a comment is a single
story ID enclosed in square brackets: ‘[#12345678]’. A more typical
message,indicating that one commit completes two stories (which need
not be in the same Tracker project),might look like this: ‘finally
[finished #12345678 #12345779],fixes client/server integration
glitch’

If an included story was not already started (it was in the “not
started” state),an update to that story from /source_commits that
doesn’t contain any other state-change information will automatically
start the story.

To automatically finish a story by using a commit message,include
“fixed”,“completed”,or “finished” in the square brackets in addition
to the story ID. You may use different cases or forms of these verbs,
such as “Fix” or “FIXES”,and they may appear before or after the
story ID. Note: For features,use of one of these keywords will put
the story in the finished state. For chores,it will put the story in
the accepted state.

In some environments,code that is committed is automatically deployed. For this situation,use the keyword “delivers” and feature stories will be put in the delivered state.

原文链接:/python/241847.html

猜你在找的Python相关文章