

#
# Conventional Commits 1.0.0
#
# <type>[optional scope]: <description>
#
# [optional references] [optional body]
#
# [optional footer]
#
# DETAILS:
#
# <type> must be one of the following:
#
# - fix: a commit of the type fix patches a bug in your codebase (this
#   correlates with PATCH in semantic versioning).
#
# - feat: a commit of the type feat introduces a new feature to the codebase
#   (this correlates with MINOR in semantic versioning).
#
# - ci: Changes to our CI configuration files and scripts
# - docs: Documentation only changes
# - style: Changes that do not affect the meaning of the code
# - refactor: A code change that neither fixes a bug nor adds a feature
# - test: Adding missing or correcting existing tests
# - chore: Changes to the build process or auxiliary tools and libraries such as
#   documentation generation
#
# BREAKING CHANGE: a commit that has a footer BREAKING CHANGE:, or appends a !
# after the type/scope, introduces a breaking API change (correlating with MAJOR
# in semantic versioning). A BREAKING CHANGE can be part of commits of any type.
#
# EXAMPLES:
#
# feat: allow provided config object to extend other configs
#
# fixes #123
#
# ---
#
# See https://www.conventionalcommits.org/en/v1.0.0/ for additional details and examples
#
