Skip to content

Commit 4da44ad

Browse files
MylesBorinsrvagg
authored andcommitted
doc: clarify who may land on an LTS staging branch
Current language is a bit confusing PR-URL: #24465 Refs: #24344 (comment) Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Gus Caplan <[email protected]> Reviewed-By: Ali Ijaz Sheikh <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Trivikram Kamat <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
1 parent dbf14ce commit 4da44ad

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

COLLABORATOR_GUIDE.md

+2-3
Original file line numberDiff line numberDiff line change
@@ -803,9 +803,8 @@ pulled from the staging branch into the LTS branch only when a release is
803803
being prepared and may be pulled into the LTS branch in a different order
804804
than they were landed in staging.
805805

806-
Any Collaborator may land commits into a staging branch, but only the release
807-
team should land commits into the LTS branch while preparing a new
808-
LTS release.
806+
Only the members of the @nodejs/backporters team should land commits onto
807+
LTS staging branches.
809808

810809
#### How can I help?
811810

0 commit comments

Comments
 (0)