Commit c554c0e
doc: clarify expectations for PR commit messages
Prior to this commit, new contributors were suggested
to use a utility to validate commit messages. Although
not inaccurate, this utility produces misleading results.
* Remove reference to `core-validate-commit`
PR-URL: #30922
Reviewed-By: Myles Borins <myles.borins@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>1 parent 4651871 commit c554c0e
1 file changed
Lines changed: 0 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -192,9 +192,6 @@ One of the existing contributors will help get things situated and the | |||
| 192 | 192 | contributor landing the Pull Request will ensure that everything follows | |
| 193 | 193 | the project guidelines. | |
| 194 | 194 | ||
| 195 | - See [core-validate-commit](https://github.com/nodejs/core-validate-commit) - | ||
| 196 | - A utility that ensures commits follow the commit formatting guidelines. | ||
| 197 | - | ||
| 198 | 195 | ### Step 5: Rebase | |
| 199 | 196 | ||
| 200 | 197 | As a best practice, once you have committed your changes, it is a good idea | |
0 commit comments