I have my own notes here: https://www.aizatto.com/engineering-code/commit-messages https://www.aizatto.com/engineering-code/commit-messages I think what I real

I have my own notes here: https://www.aizatto.com/engineering-code/commit-messages https://www.aizatto.com/engineering-code/commit-messages I think what I really like Angular's Commit Message Guidelines that suggest you include a "type" (build, docs, feature, fix, refactor) prefix into the commit message to help organize at a quick glance what the commit does. https://github.com/angular/angular/blob/master/CONTRIBUTING.md#commit https://github.com/angular/angular/blob/master/CONTRIBUTING.... Here are some other resources Erlang https://github.com/erlang/otp/wiki/Writing-good-commit-messages https://github.com/erlang/otp/wiki/Writing-good-commit-messa... Gerrit https://www.mediawiki.org/wiki/Gerrit/Commit_message_guidelines https://www.mediawiki.org/wiki/Gerrit/Commit_message_guideli...