4 ms·
The commit message still logs in the usual way, but it carries the whole set of information with it, in a way that a centralised ticket system doesn't. When a
by shakna 7y ago
The commit message still logs in the usual way, but it carries the whole set of information with it, in a way that a centralised ticket system doesn't.
When a developer is looking at logs for solving some problem, they can easily review the rationale for changes.
I'd much prefer the log explaining everything, rather than having to look to a ticket that may no longer exist.
- Chris2048 7y ago> in a way that a centralised ticket system doesn't Why doesn't it? Are closed issues not searchable? It seems to me you doubt the ticket retention, but instead of fixing that, use commits to store issues instead. How do you provide comments or updates on an issue "relevant to the commit" without arbitrary commits?
- shakna 7y ago> Why doesn't it? Are closed issues not searchable? Everywhere I have ever worked has changed ticket systems at one point, and even when they are transferred, the transfer is "lossy". Heck, just moving from one JIRA version to another can be "lossy". > How do you provide comments or updates on an issue "relevant to the commit" without arbitrary commits? In the ticket system. I was not advocating that a ticket system is pointless, because they are very useful. But a decent commit message about why a change is necessary, especially when it may not be straight forward, can save you plenty of development time further down the line.
- Chris2048 7y agoI have mixed feelings about JIRA, but if you move to a centralised ticket system you have to plan migration. If you really need to, put more detailed notes into an "Issues" file for commits/minor releases, and clear it on every major release. IMO the given example is more verbose that needed. It should give enough information about what and why a fix is done, but no more.