Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit c554c0e

Browse filesBrowse files
Derek Lewistargos
authored andcommitted
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
Copy full SHA for c554c0e

File tree

Expand file treeCollapse file tree

1 file changed

+0
-3
lines changed
Open diff view settings
Filter options
Expand file treeCollapse file tree

1 file changed

+0
-3
lines changed
Open diff view settings
Collapse file

‎doc/guides/contributing/pull-requests.md‎

Copy file name to clipboardExpand all lines: doc/guides/contributing/pull-requests.md
-3Lines changed: 0 additions & 3 deletions
  • Display the source diff
  • Display the rich diff
Original file line numberDiff line numberDiff line change
@@ -192,9 +192,6 @@ One of the existing contributors will help get things situated and the
192192
contributor landing the Pull Request will ensure that everything follows
193193
the project guidelines.
194194

195-
See [core-validate-commit](https://github.com/nodejs/core-validate-commit) -
196-
A utility that ensures commits follow the commit formatting guidelines.
197-
198195
### Step 5: Rebase
199196

200197
As a best practice, once you have committed your changes, it is a good idea

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.