git-commit-template.txt

# <type>: (If applied, this commit will...) <subject>

# Explain why this change is being made. Explain what and why vs. how.
# Provide links or keys to any relevant tickets, articles or other resources.
# |<----   Try To Limit Each Line to a Maximum Of 72 Characters   ---->|


# Uncomment the below line if you want to skip CI checks.
# [skip ci]

# Uncomment the below if adding co-authors:
# Co-authored-by: CO-AUTHOR NAME 1 <co-author@example.com>
# Co-authored-by: CO-AUTHOR NAME 2 <co-author2@example.com>

# --- COMMIT END ---
# Before committing:
#   - Are changes tested?
#   - Are changes documented?
# --------------------
# <type> can be 
#    feature  (new feature)
#    fix      (bug fix)
#    refactor (refactoring production code)
#    style    (formatting, missing semi colons, etc; no code change)
#    docs     (changes to documentation)
#    tests    (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