-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy path.gitmessage
60 lines (54 loc) · 2.05 KB
/
.gitmessage
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
58
59
#
# ------------------------------------------------------------------------------
# SUBJECT —
# ------------------------------------------------------------------------------
#
#
# ------------------------------------------------------------------------------
# BODY —
# ------------------------------------------------------------------------------
#
#
# ------------------------------------------------------------------------------
# FOOTER —
# ------------------------------------------------------------------------------
#
# Resolves: JIRA-1234
# Closes: JIRA-1357
# See Also: JIRA-1111, JIRA-2222
#
# ----------------------------------------------------------------------------------------------------------------------
# FULL EXAMPLE
# ----------------------------------------------------------------------------------------------------------------------
#
# Summarize changes in around 50 characters or less
#
# More detailed explanatory text, if necessary. Wrap it to about 72
# characters or so. In some contexts, the first line is treated as the
# subject of the commit and the rest of the text as the body. The
# blank line separating the summary from the body is critical (unless
# you omit the body entirely); various tools like `log`, `shortlog`
# and `rebase` can get confused if you run the two together.
#
# Explain the problem that this commit is solving. Focus on why you
# are making this change as opposed to how (the code explains that).
# Are there side effects or other unintuitive consequences of this
# change? Here's the place to explain them.
#
# Further paragraphs come after blank lines.
#
# - Bullet points are okay, too
#
# - Typically a hyphen or asterisk is used for the bullet, preceded
# by a single space, with blank lines in between, but conventions
# vary here
#
# If you use an issue tracker, put references to them at the bottom,
# like this:
#
# Resolves: #1234, #5678
# Closes: #2468
# See Also: #1357, #9876
#
# ----------------------------------------------------------------------------------------------------------------------
#