5 ms·
What I like to do is reference a tracking number from the issue/bug tracking system in my commit messages. Yes, this has some possible pitfalls, e.g. the sourc
by ams6110 17y ago
What I like to do is reference a tracking number from the issue/bug tracking system in my commit messages. Yes, this has some possible pitfalls, e.g. the source code may outlive the issue tracking system, or may change owners without the issue history coming along.. but it works well in practice.
- gregwebs 17y agoits best when your bug tracker can automatically link to issue numbers and commit numbers.
- makecheck 17y agoUsing svn with Trac, for example, one can use "r1234" to refer to a revision from a ticket, or "#123" to refer to a ticket number from a commit message.
- patio11 17y agoWe make extensive use of these at the day job. It is a lifesaver. If I ever get around to using bug tracking for myself, I'm certainly going to continue the practice.
- petewarden 17y agoHaving a URL scheme for bugs was a massive help at Apple, the standard for commit messages was including something like "Fix for rdar://17373108".
- modoc 17y agoYes! JIRA + Mylyn (for Eclipse) makes this automatic and let's you see the commits made for the ticket in Jira, and link from the commit e-mails to the Jira ticket(s). Huge fan.
- steveklabnik 17y agoLighthouse not only does this, but lets you modify tickets with your commits (through Github, at least). Pretty cool.
- jparise 17y agoSome SCM systems have per-commit metadata facilities. For example, Perforce changelists can be tagged with a "job" field, which could be a bug identifier.
- prodigal_erik 17y agoMicrosoft's system was pretty nice. Once you tell the bug database which commit(s) fix a bug (sometimes backed by a set of uploaded crash dumps), it keeps track of which branches the fix has been merged into, so when QA deploys a build they know what is now available to regress. They licensed Perforce for source control (rather than SourceSafe, which they long since stopped recommending anyone use, look directly into, or feed after midnight) but don't use its "job" features for this. Though it sounds like they're going to replace all this with Visual Studio Extra Crispy Team System for Epic Workgroups Prime. Best of luck prying everyone I met off vim and build.exe, guys.