-
Notifications
You must be signed in to change notification settings - Fork 2
/
.gitmessage
78 lines (76 loc) · 2.36 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
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
# Git Commit Guidelines
# =====================
#
# Each commit message consists of a header, a body and a footer. The header has
# a special format that includes a type, a scope and a subject:
#
# <type>(<scope>): <subject>
# <BLANK LINE>
# <body>
# <BLANK LINE>
# <footer>
#
# The header is mandatory and the scope of the header is optional.
#
# Any line of the commit message cannot be longer 100 characters! This allows
# the message to be easier to read on GitHub as well as in various git tools.
#
# Revert
# ======
#
# If the commit reverts a previous commit, it should begin with `revert: `,
# followed by the header of the reverted commit. In the body it should say:
# `This reverts commit <hash>.`, where the hash is the SHA of the commit being
# reverted.
#
# Type
# ====
#
# - build: Changes that affect the build system or external dependencies
# (example scopes: gulp, broccoli, npm)
# - ci: Changes to our CI configuration files and scripts (example scopes:
# Travis, Circle, BrowserStack, SauceLabs)
# - docs: Documentation only changes
# - feat: A new feature
# - fix: A bug fix
# - perf: A code change that improves performance
# - refactor: A code change that neither fixes a bug or adds a feature
# - style: Changes that do not affect the meaning of the code (white-space,
# formatting, missing semi-colons, etc)
# - test: Adding missing tests
#
# Scope
# =====
#
# The scope could be anything specifying place of the commit change.
#
# For example $location, $browser, $compile, $rootScope, ngHref, ngClick,
# ngView, etc...
#
# Subject
# =======
#
# The subject contains a succinct description of the change:
#
# - use the imperative, present tense: "change" not "changed" nor "changes"
# - don't capitalize the first letter
# - no dot (.) at the end
#
# Body
# ====
#
# Just as in the **subject**, use the imperative, present tense: "change" not
# "changed" nor "changes". The body should include the motivation for the change
# and contrast this with previous behavior.
#
# Footer
# ======
#
# The footer should contain any information about Breaking Changes and is also
# the place to reference GitHub issues that this commit Closes.
#
# Breaking Changes should start with the word BREAKING CHANGE: with a space or
# two newlines. The rest of the commit message is then used for this.
#
# original documentation:
# https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit