-
Notifications
You must be signed in to change notification settings - Fork 29
/
.git-commit-message
32 lines (31 loc) · 2.21 KB
/
.git-commit-message
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
30
31
32
############################## SUBJECT LINE ############################
#<----- Preferably use fewer than 50 chars ----->|----- 72 chars ----->#
# #
# - Begin with a leading commit verb (see below) #
# - Use the imperative mood (if applied, this commit will...) #
# - Capitalize the first word #
# - Don't end the line with a period #
# #
############################## COMMIT VERBS ############################
# #
# MAY CHANGE FUNCTIONALITY #
# Add = Create a capability e.g. feature, test, dependency #
# Cut = Remove a capability #
# Fix = Fix an issue e.g. bug, typo, accident, misstatement #
# Make = Change the build process, tooling or infrastructure #
# Start = Begin doing something e.g. create a feature flag #
# Stop = End doing something e.g. remove a feature flag #
# Bump = Increase the version of something e.g. dependency #
# #
# MUST NOT CHANGE FUNCTIONALITY #
# Refactor = A source change that aims to reduce cognitive load #
# Reformat = Refactor of formatting e.g. omit whitespace #
# Optimise = A source change that aims to improve performance #
# Document = Create explanatory comments or writings #
# #
################################## BODY ################################
# #
# - Explain the "what" and the "why" #
# - Don't explain the "how": use comments in the source for that #
# #
########################################################################