.gitcommittemplate.txt

# ----------- This is 50 characters ----------> |
# Remember to format your commit message thusly...
#
# <type>([optional scope]): <subject>
# Try to keep the subject line <=50 characters
# <BLANK LINE>
# [optional body]
# <BLANK LINE>
# [optional footer]
#
# <type> is one of:
#
#    * build: changes to the build process.
#    * ci: changes to the ci/cd.
#    * docs: documentation only change.
#    * feat or feature: a new feature was added.
#    * fix: a bug fix.
#    * refactor: code change that doesn't add a feature or fix a bug.
#    * style: change that affect code quality.
#    * test: add or correct tests.
#
# Add an exclamation point (!) before the colon (:) if this is a breaking
# change.  This should ONLY happen on fix types.
#
# <subject> should complete the following sentence:
#
#     If applied, this commit will...
#
# [optional body] is a multi-line description of the changes.  Use bulleted
# lists (-, *, etc.)to make this easier to read.
#
# [optional footer] is the place to list all the GitHub issues (if any) the
# commit closes.  These should be listed in one of the following formats:
#
#     Close: #<Issue ID>
#     Closes: #<Issue ID>
#     Fix: #<Issue ID>
#     Fixes: #<Issue ID>
#     Resolve: #<Issue ID>
#     Resolves: #<Issue ID>