如何通过提交日志将问题标记为已解决? [英] How to mark an issue as resolved from the commit log?

问题描述

我注意到在BitBucket中，当您的提交日志中包含一个类似于#12的数字时，该数字将链接到错误号12.

I noted that in BitBucket when your commit log contains a number like #12 this number is linked to the bug number 12.

我发现此功能很有趣，我想知道是否有任何关键字可以让我将问题标记为已从提交日志中解决，而不是每次都转到Web界面.

I found this feature interesting, and I wonder if there is any keyword that would allow me to mark the issue as resolved from the commit log instead of going to the web interface each time.

如果BitBucket不这样做，您能指出一个能做到这一点的系统吗?

If BitBucket doesn't do it, could you point a system that does?

推荐答案

Google Code Project Hosting也支持它:

Google Code Project Hosting also supports it:

http://code.google.com/p/support/wiki/IssueTracker#Integration_with_version_control

有用于以下目的的提交日志命令:

There are commit-log commands to:

1. 轻松将问题的状态设置为已修复".
2. 更新问题的任何方面，并添加评论.
3. 输入新问题.

4. 请求代码审查.

1. Easily set an issue's status to Fixed.
2. Update any aspect of the issue, and add a comment.
3. Enter a new issue.

4. Request a code review.

(Fixes issue NNN)    Enclose command in parentheses
Fixes issue NNN.     Full sentence in your log message description
Fixes issue NNN  On a line by itself

修复"一词可以用关闭"或解决"代替.发行号可以带或不带井号(.).

The word Fixes can replaced with Closes or Resolves. The issue number can have a leading pound-sign (#) or not.

其他commit-log命令使用更强大的多行长格式"语法.

The other commit-log commands use a multi-line "long form" syntax that is more powerful.

COMMAND-LINE
ISSUE-FIELD-UPDATE*
COMMENT-TEXT...

其中COMMAND-LINE是以下之一:

Where COMMAND-LINE is one of the following:

Update issue NNN
New issue
New review

可以有任意数目的ISSUE-FIELD-UPDATE行.这些行可以是以下之一:

There can be any number of ISSUE-FIELD-UPDATE lines. These lines can be one of the following:

Summary: NEW-VALUE
Status: NEW-VALUE
Owner: NEW-VALUE
Cc: PLUS-MINUS-LIST
Labels: PLUS-MINUS-LIST

这篇关于如何通过提交日志将问题标记为已解决?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！