iSharkFly-Docs
/
angular-docs-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs(CONTRIBUTING): sync with the change of angular/angular.js#12032 

Closes #3468
This commit is contained in:
Steve Mao 2015-08-04 21:14:52 +10:00 committed by Misko Hevery
parent c58b0ff787
commit 27aa9187f0
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
CONTRIBUTING.md
View File

@ -157,9 +157,14 @@ format that includes a **type**, a **scope** and a **subject**:
<footer> <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 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. 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 ### Type
Must be one of the following: Must be one of the following:
@ -193,6 +198,7 @@ The body should include the motivation for the change and contrast this with pre
The footer should contain any information about **Breaking Changes** and is also the place to The footer should contain any information about **Breaking Changes** and is also the place to
reference GitHub issues that this commit **Closes**. 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.
A detailed explanation can be found in this [document][commit-message-format]. A detailed explanation can be found in this [document][commit-message-format].