33 lines
979 B
Plaintext
33 lines
979 B
Plaintext
|
# If applied, this commit will ...
|
||
|
|
|
||
|
|
# Why was this change necessary? Improvements brought about by the
|
||
|
|
# change.
|
||
|
|
|
||
|
|
# End
|
||
|
|
|
||
|
|
# Format
|
||
|
|
# --------------------
|
||
|
|
# (If applied, this commit will...) <subject> (Max 72 char)
|
||
|
|
# |<---- Preferably using up to 50 chars --->|<------------------->|
|
||
|
|
# Example:
|
||
|
|
# Implement automated commit messages
|
||
|
|
|
||
|
|
# (Optional) Explain why this change is being made
|
||
|
|
# |<---- Try To Limit Each Line to a Maximum Of 72 Characters ---->|
|
||
|
|
|
||
|
|
# (Optional) Provide links or keys to any relevant tickets, articles or other resources
|
||
|
|
# Example: Github issue #23
|
||
|
|
|
||
|
|
# --- COMMIT END ---
|
||
|
|
#
|
||
|
|
# 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 "-" or "*" for bullet points in body
|
||
|
|
# --------------------
|
||
|
|
|
||
|
|
# Continuous integration messages
|