Skip to content

doc: update main branch name in release guide #43437

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nodejs-github-bot merged 2 commits into from
Jun 16, 2022
Merged

doc: update main branch name in release guide #43437

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9311408
doc: update main branch name in release guide
richardlau Jun 15, 2022
6fd1b1c
fixup! doc: update main branch name in release guide
richardlau Jun 15, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
fixup! doc: update main branch name in release guide 
Co-authored-by: Antoine du Hamel <[email protected]>
  • Loading branch information
@richardlau @aduh95
richardlau and aduh95 authored Jun 15, 2022
commit 6fd1b1c45d2f2aaa39d482bf50496c81179a6656
2 changes: 1 addition & 1 deletion doc/contributing/releases.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -387,7 +387,7 @@ release branches to more easily be passed between members of the release team if
necessary.

Create a pull request targeting the correct release line. For example, a
`v5.3.0-proposal` PR should target `v5.x`, not main. Paste the CHANGELOG
`v5.3.0-proposal` PR should target `v5.x`, not `main`. 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. If the CHANGELOG pasted into the pull request
Expand Down