.gitmessage

#
# 50-character subject line
#
# 72-character wrapped longer description. This should answer:
#
# * Why was this change necessary?
# * How does it address the problem?
# * Are there any side effects?
#
# Include a link to the ticket, if any.
#
# Follow commit message format:
#   "type(scope): message"
#
# Types can be:
#    * feat: A new feature
#    * fix: A bug fix
#    * docs: Documentation only changes
#    * style: Changes that do not affect the meaning of the code
#               (white-space, formatting, missing semi-colons, etc)
#    * refactor: A code change that neither fixes a bug or adds a feature
#    * perf: A code change that improves performance
#    * test: Adding missing tests
#    * chore: Changes to the build process or auxiliary tools and libraries
#               such as documentation generation
#