From 0688c998233a9edaead8bfa0cf44e2f64c8057e4 Mon Sep 17 00:00:00 2001 From: Derek Lewis Date: Thu, 12 Dec 2019 16:47:31 -0500 Subject: [PATCH] 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: https://github.com/nodejs/node/pull/30922 Reviewed-By: Myles Borins Reviewed-By: Anna Henningsen Reviewed-By: Gireesh Punathil Reviewed-By: Rich Trott --- doc/guides/contributing/pull-requests.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/doc/guides/contributing/pull-requests.md b/doc/guides/contributing/pull-requests.md index cd1bccd20cd691..7f4ab4e83e049b 100644 --- a/doc/guides/contributing/pull-requests.md +++ b/doc/guides/contributing/pull-requests.md @@ -192,9 +192,6 @@ One of the existing contributors will help get things situated and the contributor landing the Pull Request will ensure that everything follows the project guidelines. -See [core-validate-commit](https://github.com/nodejs/core-validate-commit) - -A utility that ensures commits follow the commit formatting guidelines. - ### Step 5: Rebase As a best practice, once you have committed your changes, it is a good idea