|
|
|
|
|
by TrainedMonkey
506 days ago
|
|
Yes, when spelunking why something has changed having good rationality would be a godsend... however let's face reality: 1. Majority of commit messages are low quality and would benefit significantly from a good summary of what was done. 2. Margin of commit messages is often too small for documenting the rationale - this job is better left for tickets. |
|
The commit message lives with the code. The number of times in my career that a company has migrated, changed, consolidated, or otherwise made all those links in commit messages obsolete, well I don't quite yet need two hands. But I see a lot of dead ends to context in code bases.