3 ms·
In the past few teams I've led, the requirement was to include a JIRA ticket number in the commit message. With tools like Fisheye, you can click from the comm
by dougdonohoe 11y ago
In the past few teams I've led, the requirement was to include a JIRA ticket number in the commit message. With tools like Fisheye, you can click from the commit message to the JIRA and get much more context about the particulars of the commit. It worked exceedingly well. The point is that there is only so much context you can put into a commit message. Sometimes the context lives outside the system and good tools support like Atlassian's suite makes life easier.
- donatj 11y agoI've seen this practice very often lead to less atomic commits, what are your thoughts?
- nirvdrum 11y agoA lot of people do something similar on GitHub. If you're going to do this, please include the issue subject in the commit message somewhere. "Fixes #135" is absolutely meaningless outside the context of whatever tool. And it absolutely falls apart if the project lives long enough to change issue trackers.
- fenomas 11y agoMuch agreed. "Fixes #123" makes sense for pull request messages, but the commit messages should be verbose!
- ekimekim 11y agoI was in a team where the tooling required a JIRA ticket reference in the commit message. Of course, the JIRA project didn't have an actual ticket for the majority of minor changes and fixes (and for that matter, adding one for every single commit in a 20-commit topic branch was tedious). Eventually the entire team was just adding "ticket 1" by default to every message. You can't solve a people problem with tooling. It can help, but ultimately if it's a pain point people will simply bypass it.