forked from X-CASH-official/xcash-core
-
Notifications
You must be signed in to change notification settings - Fork 0
/
.git-commit-template.txt
57 lines (50 loc) · 2.09 KB
/
.git-commit-template.txt
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
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
# Please use the following guidelines to format all your commit
# messages:
#
# <type>: <subject>
# <BLANK LINE>
# <body>
# <BLANK LINE>
# <footer>
# --------------------
# <type>: (If applied, this commit will...) <subject> (Max 50 char)
# |<---- Using a Maximum Of 50 Characters ---->|
# Explain why this change is being made
# |<---- Try To Limit Each Line to a Maximum Of 72 Characters ---->|
# Provide links or keys to any relevant tickets, articles or other resources
# Example: issue #23
# --- COMMIT END ---
#Please note that:
# - The HEADER is a single line of max. 50 characters that
# contains a succinct description of the change. It contains a
# type, an optional scope, and a subject
# + <type> describes the kind of change that this commit is
# providing. Allowed types are:
# * feat (feature)
# * fix (bug fix)
# * docs (documentation)
# * style (formatting, missing semicolons, …)
# * refactor
# * test (when adding missing tests)
# * chore (maintain)
# + <subject> is a very short description of the change, in
# the following format:
# * imperative, present tense: “change” not
# “changed”/“changes”
# * no capitalised first letter
# * no dot (.) at the end
# - The <body> should include the motivation for the change and
# contrast this with previous behavior and must be phrased in
# imperative present tense
# - The <footer> should contain any information about Breaking
# Changes and is also the place to reference GitHub issues that
# this commit closes
# --------------------
# 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 "-" for bullet points in body
# --------------------