According to common commit style guides, it is required to write messages in
an imperative manner. Make them actionable. Also avoid using -m as you
often need to express more detail in a long way. Here's several articles
sharing best practices:
- https://cbea.ms/git-commit/
- https://alistapart.com/article/the-art-of-the-commit/
- https://robots.thoughtbot.com/5-useful-tips-for-a-better-commit-message
- https://github.com/erlang/otp/wiki/writing-good-commit-messages
- https://wiki.openstack.org/wiki/GitCommitMessages
- https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
- https://who-t.blogspot.com/2009/12/on-commit-messages.html
- https://dev.to/gonedark/when-to-make-a-git-commit
- https://sparkbox.com/foundry/atomic_commits_with_git
- https://twitter.com/nedbat/status/1283147492616556544
- https://dhwthompson.com/2019/my-favourite-git-commit
- https://zulip.rtfd.io/en/latest/contributing/commit-discipline.html#commit-messages
Pro tip: Use Gitlint to develop a habit of writing beautiful commit messages.