Note: This Gist is deprecated. The Documentation was moved to notion.
A git commit message has three parts: header, body and footer.
The header is required and is build with a type and a summary. body and footer are optional.
Structure of a commit:
<type><(optional scope)>: <summary>
<body>
<footer>
feat
: A new featurefix
: A bug fixrefactor
: A code change that neither fixes a bug nor adds a featuredocs
: Documentation only changesci
: Changes to CI configuration files and scripts or affects the build systemperf
: A code change that improves performancetest
: Adding missing tests or correcting existing testsrevert
: Revert of a previous commit (include the commit hash in the body)
- should not more than 50 characters but at most 72.
- use the imperative, present tense (e.g. "change" not "changed" nor "changes")
- don't capitalize the first letter
- no dot (.) at the end
Imperative Hint: Summary should be able to complete the following sentence: If applied, this commit will ...
e.g. If applied, this commit willrelease version 1.0.0
A brief description of the change. See [Git Commit Good Practices]
Breaking Changes should have a BREAKING CHANGE:
with a space or two newlines. The rest of the commit message is then used for this.
See [Git Tailers]
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: '&',
myAccessor: '='
}