/
.git-message-template
36 lines (34 loc) · 1.47 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
# Please use the following guidelines to format your commit messages:
#
# <type>(<scope>): <subject>
# <BLANK LINE>
# <body>
# <BLANK LINE>
# <footer>
#
# Please note that:
# - HEADER: a single line of max. 50 characters that contains a succinct
# description of the change. It contains type, an optional scope,
# and a subject
# + <type> describes the kind of change that this commit is providing.
# Allowed types are:
# * feat or :atom: (feature)
# * fix or :bug: (bug fix)
# * docs or :bookmark_tabs: (documentation)
# * style or :bookmark_tabs: (formatting, missing semicolons, ...)
# * refactor or :wrench:
# * test or :test_tube: (when adding missing tests)
# * chore or :wrench: (maintain)
# + <scope> specifies the place of the commit change. Optional.
# + <subject> a very short description of the change.
# Use the following format:
# * imperative, present tense: "change" not
# "changed"/"changes"
# * no capitalised first letter
# * no dot (.) at the end
#
# - BODY: describe the motivation for the change and contrast it with previous
# behaviour. Use imperative present tense
#
# - FOOTER: information about Breaking Changes and also a place to reference
# GitHub issues that this commit closes