Commit d5d64c3
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -93,14 +93,17 @@ information regarding the change process: | |||
| 93 | 93 | ||
| 94 | 94 | - A `Reviewed-By: Name <email>` line for yourself and any | |
| 95 | 95 | other Collaborators who have reviewed the change. | |
| 96 | - - A `PR-URL:` line that references the full GitHub URL of the original | ||
| 96 | + - A `PR-URL:` line that references the *full* GitHub URL of the original | ||
| 97 | 97 | pull request being merged so it's easy to trace a commit back to the | |
| 98 | 98 | conversation that led up to that change. | |
| 99 | - - A `Fixes: X` line, where _X_ is either includes the full GitHub URL | ||
| 99 | + - A `Fixes: X` line, where _X_ either includes the *full* GitHub URL | ||
| 100 | 100 | for an issue, and/or the hash and commit message if the commit fixes | |
| 101 | 101 | a bug in a previous commit. Multiple `Fixes:` lines may be added if | |
| 102 | 102 | appropriate. | |
| 103 | 103 | ||
| 104 | + Review the commit message to ensure that it adheres to the guidelines | ||
| 105 | + outlined in the [contributing](https://github.com/nodejs/node/blob/master/CONTRIBUTING.md#step-3-commit) guide. | ||
| 106 | + | ||
| 104 | 107 | See the commit log for examples such as | |
| 105 | 108 | [this one](https://github.com/nodejs/node/commit/b636ba8186) if unsure | |
| 106 | 109 | exactly how to format your commit messages. | |
0 commit comments