-
Notifications
You must be signed in to change notification settings - Fork 1
/
.gitcommitmessage
29 lines (25 loc) · 1.11 KB
/
.gitcommitmessage
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
# Title: Summary, imperative mood, start upper case, don't end with a period
# Subject line should always be able to complete the following sentence:
# "If applied, this commit will (your subject line here)"
# No more than 50 chars. #### 50 chars is here: #
# Remember blank line between title and body.
# Body: Explain *what* and *why* (not *how*).
# Wrap at 72 chars. ################################## which is here: #
# At the end: Include any co-authors
# Include at least one empty line before it. Format:
# co-author: name <user@users.noreply.github.com>
#
# Reference the related issue (if there is one).
# This will automatically close the issue when merged into main. Format:
# fixes/fixed/fix/closes/close/closed #xxx
#
# 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