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
In order to have a similar structure in the commit
messages of the contributions, adding a commit
validation hook, that a subset of the structure of
angular.js validation messages.
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+28-3Lines changed: 28 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ Most of the time, when webpack does not work correctly, it might be a configurat
11
11
12
12
If you are still having difficulty after looking over your configuration carefully, please post
13
13
a question to [StackOverflow with the webpack-cli tag](http://stackoverflow.com/tags/webpack-cli). Questions
14
-
that include your webpack.config.js and relevant files, this way you help others to help you.
14
+
that include your `webpack.config.js` and relevant files, this way you help others to help you.
15
15
16
16
**If you have discovered a bug or have a feature suggestion, feel free to create an issue on Github.**
17
17
@@ -21,7 +21,7 @@ that include your webpack.config.js and relevant files, this way you help others
21
21
*Note: Node 6 or greater would be better for "best results".*
22
22
* Fork the **webpack-cli** repo at [https://github.com/webpack/webpack-cli](https://github.com/webpack/webpack-cli).
23
23
*`git clone <your-clone-url> && cd webpack-cli`
24
-
*`git checkout develop`
24
+
*Install the commit validator: `npm run install-commit-validator`
25
25
26
26
### Setup with npm
27
27
* Install the dependencies: `npm install`
@@ -86,6 +86,31 @@ In case you've got a small change in most of the cases your pull request would b
86
86
* Follow the existing coding style
87
87
* Write a [good commit message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html)
88
88
89
+
## Commit message format
90
+
91
+
Our commit messages format follows the [angular.js commits format](https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit-message-format).
92
+
93
+
We don't use the scope. The template of a commit would look like this:
94
+
95
+
### Commit Message Format
96
+
Each commit message consists of a **header**, a **body** and a **footer**. The header has a special
97
+
format that includes a **type** and a **subject**:
98
+
99
+
```
100
+
<type>: <subject>
101
+
<BLANK LINE>
102
+
<body>
103
+
<BLANK LINE>
104
+
<footer>
105
+
```
106
+
107
+
The **header** is mandatory.
108
+
109
+
Any line of the commit message cannot be longer 100 characters. This allows the message to be easier
110
+
to read on GitHub as well as in several git tools.
111
+
112
+
For more information about what each part of the template mean, head up to the documentation in the
0 commit comments