> I don’t understand why the history of the code matters so much to some people.
Having the git blame output of the line I'm changing is very helpful when determining the potential consequences of changing that line. If the history doesn't matter, then why bother with commit messages at all. You could essentially script your editor to run "git commit -a --allow-empty --allow-empty-message" every time you write the files to disk.
Our workflow is:
- branch
- commit first version, open Github PR with a text describing the PR, which is usually longer than the git commit message and contains links to notion pages and other things detailing the design
- reviewers look at the code, and there is some to and fro with smaller commits until the PR is fine
- code gets merged
So the main action happens outside of git. Maybe for other workflows git commit messages are more important.
Having the git blame output of the line I'm changing is very helpful when determining the potential consequences of changing that line. If the history doesn't matter, then why bother with commit messages at all. You could essentially script your editor to run "git commit -a --allow-empty --allow-empty-message" every time you write the files to disk.