Github 和 Fogbugz

发布于 2024-10-17 13:03:35 字数 328 浏览 9 评论 0 原文

所以我们集成了fogbugz和github，实际机制似乎可以工作。（即，当按下 github 上的“测试”按钮时，会显示“有效负载已交付”消息）不幸的是，无法找到有关在提交消息中放入哪些内容以将错误与提交联系起来的文档。

我已经尝试过

git commit -am 'fixing 97047'
git push origin

，但

git commit -am 'fixing #97047'
git push origin

似乎都不起作用。我很想知道我缺少什么 - 非常感谢文档链接！

原文

So we have integrated fogbugz and github, the actual mechanism seems to work. (i.e. when pushing the "test" button on github, the message "payload delivered" is shown) Unfortunately, cannot find the documentation on what to put in the commit message to tie the bug to the commit.

I have tried

git commit -am 'fixing 97047'
git push origin

and

git commit -am 'fixing #97047'
git push origin

Neither seems to work. Would love to know what I'm missing - links to documentation would be most appreciated!

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

我最亲爱的 2024-10-24 13:03:35

案例编号应采用以下形式：

\b((FogBug[sz]|Case|Bug[zs]*(?:ID)*):(\d+)

   FogBugz:1234
   FogBugs:1234
   Case:1234
   Bugz:1234

should all work.

我使用 FogBugzId:1234

The case number should be of the form:

\b((FogBug[sz]|Case|Bug[zs]*(?:ID)*):(\d+)

   FogBugz:1234
   FogBugs:1234
   Case:1234
   Bugz:1234

should all work.

I use FogBugzId:1234

回复收藏 0 原文

ゝ杯具 2024-10-24 13:03:35

源代码的 URL 已更改为 https:// github.com/github/github-services/blob/master/lib/services/fog_bugz.rb

此外，RE 已更改为：

/\s*(?:Bug[zs]*\s*IDs*\s*|Case[s]*)[#:; ]+((\d+[ ,:;#]*)+)/i)

这意味着，例如单词“FogBugz”将不再在检查中起作用- 在评论中。它必须类似于“Bug IDs:123”或“Case:123”以及 FogBugz 案例编号才能被识别。

The URL to the source code has changed to https://github.com/github/github-services/blob/master/lib/services/fog_bugz.rb

Also, the RE has changed to:

/\s*(?:Bug[zs]*\s*IDs*\s*|Case[s]*)[#:; ]+((\d+[ ,:;#]*)+)/i)

Which means, for example the word "FogBugz" will no longer work in the check-in comment. It will have to be something like "Bug IDs:123" or "Case:123" along with the FogBugz case number in order to be recognized.

回复收藏 0 原文

~没有更多了~