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
+2Lines changed: 2 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -187,6 +187,8 @@ We have very precise rules over how our git commit messages can be formatted. T
187
187
readable messages** that are easy to follow when looking through the **project history**. But also,
188
188
we use the git commit messages to **generate the AngularJS change log**.
189
189
190
+
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.
191
+
190
192
### Commit Message Format
191
193
Each commit message consists of a **header**, a **body** and a **footer**. The header has a special
192
194
format that includes a **type**, a **scope** and a **subject**:
0 commit comments