# Title: Summary, imperative, start upper case, don't end with a period
# If applied, this commit will <your Title>

# Body: Explain *what* and *why* (not *how*).


# BREAKING CHANGE: <description>
# Fixes: #
# Refs: #
# Co-authored-by: <name> <email>



# Convention Commits (https://www.conventionalcommits.org/en/v1.0.0/ or https://github.com/angular/angular/blob/85b4941be137a2fcdc664dc870e408dd72ad7de7/CONTRIBUTING.md#commit):
#  feat: [Features] -> MINOR version bump
#      A new feature
#
#  fix: [Bug Fixes] -> PATCH version bump
#      A bug fix
#
#  append '!' after the type/scope: [Breaking Change] -> MAJOR version bump
#      A breaking API change
#
#  docs: [Documentation]
#      Documentation only changes
#
#  style: [Styles]
#      Changes that do not affect the meaning of the code
#      (white-space, formatting, missing semi-colons, etc)
#
#  refactor: [Code Refactoring]
#      A code change that neither fixes a bug nor adds a feature
#
#  perf: [Performance Improvements] -> PATCH version bump
#      A code change that improves performance
#
#  test: [Tests]
#      Adding missing tests or correcting existing tests
#
#  build: [Builds] -> PATCH version bump
#      Changes that affect the build system or external dependencies
#      (example scopes: gulp, broccoli, npm)
#
#  ci: [Continuous Integrations]
#      Changes to our CI configuration files and scripts
#      (example scopes: Travis, Circle, BrowserStack, SauceLabs)
#
#  chore: [Chores]
#      Other changes that don't modify src or test files
#
#  reverts: [Reverts]
#      Reverts a previous commit

# How to Write a Git Commit Message:
# [https://chris.beams.io/posts/git-commit/] -> https://cbea.ms/git-commit/
#
# 1. Separate subject from body with a blank line
# 2. Limit the subject line to 50 characters
# 3. Capitalize the subject line
# 4. Do not end the subject line with a period
# 5. Use the imperative mood in the subject line
# 6. Wrap the body at 72 characters
# 7. Use the body to explain *what* and *why* vs. *how*
#
# vim: ft=gitcommit