Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • 2
    Consider CI systems like Jenkins, which know nothing about branches, just commits. If you want to tie Jenkins back to eg JIRA, to put build-related comments on JIRA tickets which some people think is a useful thing to do, then you need the ticket number in the commit. Or, take git bisect. It reports to me what commit it's on, and in some cases it would highly useful to have the ticket number in that commit msg. Commented Jan 23, 2016 at 4:02
  • 2
    Branch names in some VCS's are strictly temporary; in git, there is no way to look at a commit and determine which branch the user had checked out when it was made, the only place where a ticket can be referenced is the commit message. Commented Jan 28, 2024 at 17:54