.gitmessage

# <type>: <subject> (max 50 chars)
# |<----  Using a Maximum Of 50 Characters  ---->|

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

# Provide links or keys to any relevant tickets, articles or other resources
# Example: Github issue #23

# --- COMMIT END ---
# Type can be:
#    feat     (new feature)
#    fix      (bug fix)
#    refactor (refactoring 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 build tasks, package manager configs, etc)
#    perf     (performance improvements)
#    ci       (continuous integration related)
#    build    (build system or external dependencies)
#    revert   (reverting a previous commit)
# --------------------
# Remember to:
#   * 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
# --------------------
# Emoji guide (optional):
#   ✨ feat     🐛 fix       📚 docs
#   🧹 refactor 🧪 test      🔧 chore
#   ⚡ perf     🚀 deploy    🔥 remove
#   💚 ci       📦 build     ⏪ revert
# --------------------