It goes without saying that commits should include tests that cover the change, where possible. > immutably That's what makes this modus operandi so powerful

It goes without saying that commits should include tests that cover the change, where possible. > immutably That's what makes this modus operandi so powerful IMO - comments in code may go unmaintained, tests may start failing for other reasons, issue trackers come and go, developers leave the company, documentation rots. The commit message is (unless you have a bad actor) immutably linked to the original change, and that's exactly why you should be thorough in expressing its reason for being. I can git checkout the point in time (perhaps having bisected) and have the information to allow me to reproduce the issue.