-
Notifications
You must be signed in to change notification settings - Fork 0
/
.gitmessage
179 lines (162 loc) · 4.85 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
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
# commit message template
#=================#
# <type>(<scope>): <subject>
# <BLANK LINE>
# <body>
# <BLANK LINE>
# <footer>
#=================#
# 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.
## Subject line
# Subject line contains succinct description of the change.
# Allowed `<type>`
# feat (feature)
# fix (bug fix)
# docs (documentation)
# style (formatting, missing semi colons, …)
# refactor
# test (when adding missing tests)
# chore (maintain)
# Allowed `<scope>`
# Scope could be anything specifying place of the commit change. For example $location, $browser, $compile, $rootScope, ngHref, ngClick, ngView, etc...
# `<subject>` text
# - use imperative, present tense: “change” not “changed” nor “changes”
# - don't capitalize first letter
# - no dot (.) at the end
## Message body
# - just as in <subject> use imperative, present tense: “change” not “changed” nor “changes”
# - includes motivation for the change and contrasts with previous behavior
# http://365git.tumblr.com/post/3308646748/writing-git-commit-messages
# http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
## Message footer
# Breaking changes
# All breaking changes have to be mentioned in footer with the description of the change, justification and migration notes
# ```
# BREAKING CHANGE: isolate scope bindings definition has changed and
# the inject option for the directive controller injection was removed.
#
# To migrate the code follow the example below:
#
# Before:
#
# scope: {
# myAttr: 'attribute',
# myBind: 'bind',
# myExpression: 'expression',
# myEval: 'evaluate',
# myAccessor: 'accessor'
# }
#
# After:
#
# scope: {
# myAttr: '@',
# myBind: '@',
# myExpression: '&',
# // myEval - usually not useful, but in cases where the expression is assignable, you can use '='
# myAccessor: '=' // in directive's template change myAccessor() to myAccessor
# }
#
# The removed `inject` wasn't generaly useful for directives so there should be no code using it.
# ```
# Referencing issues
# Closed bugs should be listed on a separate line in the footer prefixed with "Closes" keyword like this:
# ```
# Closes #234
# ```
#
# or in case of multiple issues:
#
# ```
# Closes #123, #245, #992
# ```
## Example
# ```
# feat($browser): onUrlChange event (popstate/hashchange/polling)
#
# Added new event to $browser:
# - forward popstate event if available
# - forward hashchange event if popstate not available
# - do polling when neither popstate nor hashchange available
#
# Breaks $browser.onHashChange, which was removed (use onUrlChange instead)
# ```
#
# ```
# fix($compile): couple of unit tests for IE9
#
# Older IEs serialize html uppercased, but IE9 does not...
# Would be better to expect case insensitive, unfortunately jasmine does
# not allow to user regexps for throw expectations.
#
# Closes #392
# Breaks foo.bar api, foo.baz should be used instead
# ```
#
# ```
# feat(directive): ng:disabled, ng:checked, ng:multiple, ng:readonly, ng:selected
#
# New directives for proper binding these attributes in older browsers (IE).
# Added coresponding description, live examples and e2e tests.
#
# Closes #351
# ```
#
# ```
# style($location): add couple of missing semi colons
# ```
#
# ```
# docs(guide): updated fixed docs from Google Docs
#
# Couple of typos fixed:
# - indentation
# - batchLogbatchLog -> batchLog
# - start periodic checking
# - missing brace
# ```
#
# ```
# feat($compile): simplify isolate scope bindings
#
# Changed the isolate scope binding options to:
# - @attr - attribute binding (including interpolation)
# - =model - by-directional model binding
# - &expr - expression execution binding
#
# This change simplifies the terminology as well as
# number of choices available to the developer. It
# also supports local name aliasing from the parent.
#
# BREAKING CHANGE: isolate scope bindings definition has changed and
# the inject option for the directive controller injection was removed.
#
# To migrate the code follow the example below:
#
# Before:
#
# scope: {
# myAttr: 'attribute',
# myBind: 'bind',
# myExpression: 'expression',
# myEval: 'evaluate',
# myAccessor: 'accessor'
# }
#
# After:
#
# scope: {
# myAttr: '@',
# myBind: '@',
# myExpression: '&',
# // myEval - usually not useful, but in cases where the expression is assignable, you can use '='
# myAccessor: '=' // in directive's template change myAccessor() to myAccessor
# }
#
# The removed `inject` wasn't generaly useful for directives so there should be no code using it.
# ```
## Reference
# https://gist.github.com/stephenparish/9941e89d80e2bc58a153#format-of-the-commit-message
## Usage
# git config --local commit.template .gitmessage
# git config --local --unset commit.template