> The latter two are better explained by comments in the code Totally agree. Commit metadata is nice to have, but ultimately I think good code mostly explains

> The latter two are better explained by comments in the code Totally agree. Commit metadata is nice to have, but ultimately I think good code mostly explains "how" by the code itself, and "why" should be comments. Especially for local context, where the why has to do with some other bit of code. Individual commit messages are also secondary to the pull request merge commit, which should have a better explanation of the goal, or tie it to a task, etc.