When people have external systems, the basic problem they face is that those systems seem to be redundant with the information in the commit log. Why write the same thing twice, when the commit log can just point to the ticket, which undoubtedly has a lot of rationale and reasoning already written into it?
But in my experience, it’s far more useful to have good commit log messages. When hunting in the code for a problem, the commit log is right there and available to tools like
git log --grep, which can also print the diff alongside the log messages.
And while some tools like GitHub pull requests offer line-by-line commentary on diffs, the other interesting thing about commit logs is that they’ve proven much more resilient over time. Our ticket tracking has migrated from my boss’s inbox, to Lighthouse, to a bespoke ticketing system… that we integrated into our support team’s workflow as well, which has become something we want to split back out. And then we might replace the “remaining half” of the bespoke system with some off-the-shelf solution.
Meanwhile, our commit logs have been preserved, even across a move from subversion to git, so those go back to the point in time where the founders realized they should set it up. But the references to “Lighthouse” have been broken for years, and if we succeed in killing a huge pile of custom code nobody wants to maintain, all those “ticket #16384” references are also going to be useless.
But the commit messages will live on, in a way that ticketing systems have not. And so, I don’t really trust that we’d stick to GitHub and have their issue and pull request systems available for every change, forever.
Aside from that, I think a succinct summary of the ticket makes a good commit message. I try to avoid repeating all the ticket babble, status updates, and dead ends in the commit:
Contoso requested that their cancellations be calculated on a 90-day cliff instead of days remaining in term. Add
cancel_cliff_days=90to the client settings. Ticket 18444.
This gives the big-picture outlook on what happened and why, and lets the diff speak for itself on whether the change suits the intention. If there are questions about whether the true intention was understood, then the ticket is still linked, so it can be examined in further detail.