You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 12, 2024. It is now read-only.
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+7-3
Original file line number
Diff line number
Diff line change
@@ -209,7 +209,9 @@ We have very precise rules over how our git commit messages can be formatted. T
209
209
readable messages** that are easy to follow when looking through the **project history**. But also,
210
210
we use the git commit messages to **generate the AngularJS change log**.
211
211
212
-
The commit message formatting can be added using a typical git workflow or through the use of a CLI wizard ([Commitizen](https://github.com/commitizen/cz-cli)). To use the wizard, run `npm run commit`in your terminal after staging your changes in git.
212
+
The commit message formatting can be added using a typical git workflow or through the use of a CLI
213
+
wizard ([Commitizen](https://github.com/commitizen/cz-cli)). To use the wizard, run `yarn run commit`
214
+
in your terminal after staging your changes in git.
213
215
214
216
### Commit Message Format
215
217
Each commit message consists of a **header**, a **body** and a **footer**. The header has a special
@@ -229,7 +231,8 @@ Any line of the commit message cannot be longer 100 characters! This allows the
229
231
to read on GitHub as well as in various git tools.
230
232
231
233
### Revert
232
-
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.
234
+
If the commit reverts a previous commit, it should begin with `revert: `, followed by the header of the reverted commit.
235
+
In the body it should say: `This reverts commit <hash>.`, where the hash is the SHA of the commit being reverted.
233
236
234
237
### Type
235
238
Must be one of the following:
@@ -266,7 +269,8 @@ The body should include the motivation for the change and contrast this with pre
266
269
The footer should contain any information about **Breaking Changes** and is also the place to
267
270
[reference GitHub issues that this commit closes][closing-issues].
268
271
269
-
**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.
272
+
**Breaking Changes** should start with the word `BREAKING CHANGE:` with a space or two newlines.
273
+
The rest of the commit message is then used for this.
270
274
271
275
A detailed explanation can be found in this [document][commit-message-format].
0 commit comments