.gitmessage

# <type>: <subject>
# |<----  Using a Maximum Of 50 Characters  ---->|

# Explain why this change is being made
# |<----   Try To Limit Each Line to a Maximum Of 72 Characters   ---->|

# --- COMMIT END ---
# Type can be
#    feat     (new feature)
#    fix      (bug fix)
#    refactor (refactoring production code)
#    style    (formatting, missing semi colons, etc; no code change)
#    docs     (changes to documentation)
#    test     (adding or refactoring tests; no production code change)
#    chore    (updating grunt tasks etc; no production code change)
# --------------------
# Remember to
#   - Capitalize the subject line
#   - Use the imperative mood in the subject line
#   - Do not end the subject line with a period
#   - Separate subject from body with a blank line
#   - Use the body to explain what and why vs. how
#   - Can use multiple lines with "-" for bullet points in body
# --------------------
# For major changes, use one of these formats:
#
# 1. In the commit body:
#    feat: add new authentication system
#
#    BREAKING CHANGE: The authentication API has been completely redesigned.
#    All existing authentication tokens will be invalidated.
#
# 2. In the subject line:
#    feat!: redesign authentication system
#
#    The authentication API has been completely redesigned.
#    All existing authentication tokens will be invalidated.
#
# Note: Both formats will trigger a major version bump.