git commit message template

.gitmessage.txt

# < declarative subject > (Max 50 char)
# One of ["feat","fix","docs","style","refactor","perf","test","chore"]:
# |<----  Using a Maximum Of 50 Characters  ---->|


# Explain why this change is being made
# |<----   Try To Limit Each Line to a Maximum Of 72 Characters   ---->|


# More detailed explanatory text, if necessary. The blank line
# separating the summary from the body is critical (unless you omit the
# body entirely); various tools like `log`, `shortlog` and `rebase` can
# get confused if you run the two together.
#
# Explain the problem that this commit is solving. Focus on *why* you
# are making this change as opposed to how (the code explains that).
# Are there side effects or other unintuitive consequences of this
# change? Here's the place to explain them.

# Provide links or keys to any relevant tickets, articles or other resources
# Resolves: DO-200
# See Also: DO-201, D0-202

# From https://chris.beams.io/posts/git-commit/
# and https://gist.github.com/adeekshith/cd4c95a064977cdc6c50
# and https://github.com/angular/angular.js/blob/master/DEVELOPERS.md#commits

setup-git-message.sh

git config commit.template ~/.gitmessage.txt