.gitmessage

# Header (mandatory)
# <type>[optional scope]: <short summary>
# |<----  Using a Maximum Of 50 Characters  ---->|


# Body (optional)
# Explain what, and why this change is being made
# |<----   Try To Limit Each Line to a Maximum Of 72 Characters   ---->|


# Footer (optional)
# Provide links or keys to any relevant tickets, articles or other resources
# Example: Closes #1, fixes #2, resolves #3
# Breaking changes should start with the word "BREAKING CHANGES:" followed by space
# Example: BREAKING CHANGES: config filename changed

# --- COMMIT END ---
# Type can be
#    build    (affects build components, e.g. ci pipeline, dependencies)
#    chore    (miscellaneous changes, e.g. modifying .gitignore)
#    docs     (changes to documentation)
#    feat     (new feature)
#    fix      (bug fix)
#    perf     (refactor commit that improves performance)
#    refactor (rewrite/restructure code that does not change behaviour)
#    style    (formatting, missing semi colons, etc; no code change)
#    test     (adding or correcting tests)
# --------------------
# Remember to
#   - Use the imperative, present tense: "change" not "changed" nor "changes"
#   - Don't capitalize the subject line
#   - Don't end the subject line with a period
#   - Separate subject from body with a blank line
#   - Separate body from footer with a blank line
#   - Use the body to explain what and why vs. how
#   - Can use multiple lines with "-" for bullet points in body
# --------------------