OSSForks/node
1
0
Fork 0
mirror of https://github.com/zebrajr/node.git synced 2026-01-15 12:15:26 +00:00
Code Issues Actions 8 Packages Projects Releases Wiki Activity

doc: add text about moving long commit lists out of PR description

Browse Source 
PR-URL: https://github.com/nodejs/node/pull/39186
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Beth Griggs <bgriggs@redhat.com>
Reviewed-By: Michael Dawson <midawson@redhat.com>
This commit is contained in:
Danielle Adams
2021-06-28 12:58:22 -04:00
parent f0838a09f1
commit 223625a0b9
1 changed files with 13 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
doc/guides/releases.md
View File

@@ -398,7 +398,19 @@ Create a pull request targeting the correct release line. For example, a
`v5.3.0-proposal` PR should target `v5.x`, not master. Paste the CHANGELOG
modifications into the body of the PR so that collaborators can see what is
changing. These PRs should be left open for at least 24 hours, and can be
updated as new commits land.
updated as new commits land. If the CHANGELOG pasted into the pull request
is long enough that it slows down the GitHub UI, consider pasting the commits
into `<details>` tags or in follow up comments.
If using the `<details>` tag, use the following format:
```markdown
<details>
<summary>Commits</summary>
* Full list of commits...
</details>
```
If you need any additional information about any of the commits, this PR is a
good place to @-mention the relevant contributors.