| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
1 parent 7c7228e commit 6d6a65e
2 files changed
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -13,7 +13,9 @@ Contributors guide: https://github.com/nodejs/node/blob/master/CONTRIBUTING.md | |||
| 13 | 13 | - [ ] `make -j4 test` (UNIX), or `vcbuild test nosign` (Windows) passes | |
| 14 | 14 | - [ ] tests and/or benchmarks are included | |
| 15 | 15 | - [ ] documentation is changed or added | |
| 16 | - - [ ] commit message follows commit guidelines | ||
| 16 | + - [ ] commit message follows [commit guidelines][] | ||
| 17 | 17 | ||
| 18 | 18 | ##### Affected core subsystem(s) | |
| 19 | 19 | <!-- Provide affected core subsystem(s) (like doc, cluster, crypto, etc). --> | |
| 20 | + | ||
| 21 | + [commit guidelines]: https://github.com/nodejs/node/blob/master/CONTRIBUTING.md#commit-guidelines | ||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -95,6 +95,8 @@ $ git add my/changed/files | |||
| 95 | 95 | $ git commit | |
| 96 | 96 | ``` | |
| 97 | 97 | ||
| 98 | + ### Commit guidelines | ||
| 99 | + | ||
| 98 | 100 | Writing good commit logs is important. A commit log should describe what | |
| 99 | 101 | changed and why. Follow these guidelines when writing one: | |
| 100 | 102 | ||
| Back | FazBrowse Home | New Git URL |
0 commit comments