Using Git commit message templates to write better commit messages
This is a good idea, but in practice after a few commits you learn all the principles and don't need a wall of text in your commit template. Getting feedback in your PRs about your commit messages helps quickly reinforce learning these best practices. (you do review the commit message when doing PRs, right? ;)I'm a big fan of Conventional Commits[1], so my commit template reminds me of the types and provides an actual template to describe my change:    (optional scope):
    # type: build ci chore docs feat fix perf refactor revert style test
 
    Problem:
 
    Solution:
 
    Testing:
 
    Issue:

Where Problem describes why this change is needed, Solution is what this change delivers, and Testing is how this change was validated. Issue is the JIRA/Github issue related to this change.EDIT: The Problem/Solution/Testing/Issue is not part of Conventional Commits, I added those to give structure to the body.[1] https://www.conventionalcommits.org/en/v1.0.0/