(Any of the three will work.) Note that this will link to the issue and also close it. You can find out more in this blog post (start watching the embedded video at about 1:40).

I'm not sure if a similar syntax will simply link to an issue without closing it.

回复收藏 0 原文

乖乖哒 2024-08-18 02:39:50

github 添加对包含 #issuenbr 的提交的引用（偶然发现的）。

回复收藏 0 原文

掩于岁月 2024-08-18 02:39:50

您还可以交叉引用存储库：

githubuser/repository#xxx

xxx 是问题编号

You can also cross reference repos:

githubuser/repository#xxx

xxx being the issue number

回复收藏 0 原文

错爱 2024-08-18 02:39:50

他们在博客上写了一篇关于新问题 2.0 的精彩文章
https://github.blog/2011-04- 09-issues-2-0-the-next- Generation/

同义词包括

fixes #xxx
fix #xxx
fix #xxx
closes #xxx
close #xxx
close #xxx

在提交消息中使用任何关键字都会使您的提交提到的问题或关闭问题。

回复收藏 0 原文

冰雪梦之恋 2024-08-18 02:39:50

为了将问题编号链接到您的提交消息，您应该添加：
git 提交消息中的 #issue_number。

提交消息示例 Udacity Git 提交消息风格指南

feat: Summarize changes in around 50 characters or less

More detailed explanatory text, if necessary. Wrap it to about 72
characters or so. In some contexts, the first line is treated as the
subject of the commit and the rest of the text as the body. The
blank line separating the summary from the body is critical (unless
you omit the body entirely); various tools like `log`, `shortlog`
and `rebase` can get confused if you run the two together.

Explain the problem that this commit is solving. Focus on why you
are making this change as opposed to how (the code explains that).
Are there side effects or other unintuitive consequenses of this
change? Here's the place to explain them.

Further paragraphs come after blank lines.

 - Bullet points are okay, too

 - Typically a hyphen or asterisk is used for the bullet, preceded
   by a single space, with blank lines in between, but conventions
   vary here

If you use an issue tracker, put references to them at the bottom,
like this:

Resolves: #123
See also: #456, #789

您还可以参考存储库：

githubuser/repository#issue_number

In order to link the issue number to your commit message, you should add:
#issue_number in your git commit message.

Example Commit Message from Udacity Git Commit Message Style Guide

feat: Summarize changes in around 50 characters or less

More detailed explanatory text, if necessary. Wrap it to about 72
characters or so. In some contexts, the first line is treated as the
subject of the commit and the rest of the text as the body. The
blank line separating the summary from the body is critical (unless
you omit the body entirely); various tools like `log`, `shortlog`
and `rebase` can get confused if you run the two together.

Explain the problem that this commit is solving. Focus on why you
are making this change as opposed to how (the code explains that).
Are there side effects or other unintuitive consequenses of this
change? Here's the place to explain them.

Further paragraphs come after blank lines.

 - Bullet points are okay, too

 - Typically a hyphen or asterisk is used for the bullet, preceded
   by a single space, with blank lines in between, but conventions
   vary here

If you use an issue tracker, put references to them at the bottom,
like this:

Resolves: #123
See also: #456, #789

You can also reference the repositories:

githubuser/repository#issue_number

回复收藏 0 原文

甜是你 2024-08-18 02:39:50

正如其他答案的补充：如果您甚至不想编写带有问题编号的提交消息并且碰巧使用 Eclipse 进行开发，那么您也可以安装 eGit 和 Mylyn 插件作为 Mylyn 的 GitHub 连接器。然后，Eclipse 可以自动跟踪您正在处理的问题，并自动填写提交消息，包括所有其他答案中显示的问题编号。

有关该设置的更多详细信息，请参阅 http://wiki.eclipse.org/EGit/GitHub/UserGuide< /a>

回复收藏 0 原文