Git 与错误跟踪的集成：它可以跟踪合并吗？
我正在研究具有 git 后端的各种错误跟踪（bt）系统，它们似乎都依赖于在提交消息中添加特定于 bt 的标签，作为确定将提交映射到哪个错误的方法。
鉴于 git 在合并/拉取/cherry-picks 完成时保留提交历史记录，所有这些提交（可能来自外部各方，例如上游）将不会有任何特定于 bt 的标签，因此不会显示在错误跟踪系统中。在我看来，除了由同一个人/团队/组织完全开发的项目（然后总是将 bt 特定标签添加到提交消息中）之外，这似乎使其对任何 git 项目都没用。
我在这里错过了什么吗？有没有一种方法可以让这些 git-to-bt 集成工作，并且还可以捕获通过合并传入的外部提交？我浏览了各种错误跟踪系统（redmine、trac、jira 等）的描述，但找不到任何说明它们如何使用此系统的文档（它们通常仅在文档中提供单个提交示例） ）。
I'm looking at the various bugtracking(bt) systems that have git backends, and they all seem to rely on adding a bt-specific tag to the commit message, as a way to determine which bug to map the commit to.
Given that git retains the commit history when merges/pulls/cherry-picks are done, all of those commits (that might come from outside parties such as upstream) will not have any bt-specific tag in them, and thus will not show up in the bugtracking system. Which in my view seems to make it useless for any git project other than ones fully developed by the same person/team/organization (which would then always add the bt-specific tag to the commit messages).
Am I missing something here? Is there a way that these git-to-bt integrations work that can also capture outside commits coming in through merges? I've looked through the descriptions of various bugtracking systems (redmine, trac, jira, etc...) and I can't find any documentation that would indicate how they work with this (they usually have single commit examples in the docs only).
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我唯一能想到的是，你可以在上游分支中合并，但告诉git不要用
--no-commit提交合并结果，然后用git commit添加您的错误跟踪器参考。否则我不知道错误跟踪器如何足够聪明，知道如何将错误编号映射到提交 ID。The only thing I can think of is that you can merge in the upstream branch, but tell git not to commit the merge results with
--no-commitand thengit committo add your bug-tracker reference. Otherwise I don't know how a bug tracker can be smart enough to know how to map bug numbers to commit IDs.