-
Notifications
You must be signed in to change notification settings - Fork 3
/
.git-message-template
41 lines (40 loc) · 1.67 KB
/
.git-message-template
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
# Hey there o/!
#
# We just wanted to let you know that we care a great deal about making
# our git history clean, maintainable and easy to access for all our
# contributors. Commit messages are very important to us, which is why
# we have a strict commit message policy in place. Please use the following
# guidelines to format all your commit messages:
#
# <type>(<scope>): <subject>
# <BLANK LINE>
# <body>
# <BLANK LINE>
# <footer>
#
# 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 semi colons, …)
# * refactor
# * test (when adding missing tests)
# * chore (maintain)
# + <scope> can be anything specifying place of the commit change
# + <subject> is a very short description of the change, in the
# following format:
# * imperative, present tense: “change” not “changed” / “changes”
# * no capitalized 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
#
# Thank you <3