28 lines
949 B
Plaintext
28 lines
949 B
Plaintext
# Note: anything starting with '#' is removed by git
|
|
# Title: Short summary of what has changed
|
|
|
|
# use the convention below, give more details in the body
|
|
|
|
# add release, component, variant, file, module
|
|
# remove component, variant, file, module
|
|
# change file, component value, circuit, aesthetics, module
|
|
|
|
# No more than 50 chars. #### 50 chars is here: #
|
|
|
|
# Remember blank line between title and body.
|
|
|
|
# Body: Explain *what* and *why* (not *how*). Include task ID (Jira issue).
|
|
# Wrap at 72 chars. ################################## which is here: #
|
|
|
|
|
|
|
|
# How to Write a Git Commit Message:
|
|
# https://chris.beams.io/posts/git-commit/
|
|
#
|
|
# 1. Separate subject from body with a blank line
|
|
# 2. Limit the subject line to 50 characters
|
|
# 3. Capitalize the subject line
|
|
# 4. Do not end the subject line with a period
|
|
# 5. Use the imperative mood in the subject line
|
|
# 6. Wrap the body at 72 characters
|
|
# 7. Use the body to explain what and why vs. how |