From d591a59ac1d654070cd1f0b8b7cb1ff479426f67 Mon Sep 17 00:00:00 2001 From: Vse Mozhet Byt Date: Sun, 22 Apr 2018 03:35:12 +0300 Subject: [PATCH] meta: document commit msg exception for long URLs PR-URL: https://github.com/nodejs/node/pull/20207 Fixes: https://github.com/nodejs/node/issues/17116 Refs: https://github.com/nodejs/core-validate-commit/issues/24 Reviewed-By: Ruben Bridgewater Reviewed-By: Luigi Pinca Reviewed-By: Trivikram Kamat --- doc/guides/contributing/pull-requests.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/guides/contributing/pull-requests.md b/doc/guides/contributing/pull-requests.md index b6cc9eeeefc745..f481a2cacb9f01 100644 --- a/doc/guides/contributing/pull-requests.md +++ b/doc/guides/contributing/pull-requests.md @@ -151,7 +151,7 @@ A good commit message should describe what changed and why. 2. Keep the second line blank. -3. Wrap all other lines at 72 columns. +3. Wrap all other lines at 72 columns (except for long URLs). 4. If your patch fixes an open issue, you can add a reference to it at the end of the log. Use the `Fixes:` prefix and the full issue URL. For other references