Skip to content

doc: clarify revert PR label policy - #66529

Open
aduh95 wants to merge 1 commit into
nodejs:mainfrom
aduh95:revert-labels
Open

aduh95 wants to merge 1 commit into
nodejs:mainfrom
aduh95:revert-labels

Conversation

@aduh95

@aduh95 aduh95 commented Oct 5, 2026

Copy link
Copy Markdown
Contributor

No description provided.

Signed-off-by: Antoine du Hamel <duhamelantoine1995@gmail.com>
@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

Review requested:

  • @nodejs/tsc

@nodejs-github-bot nodejs-github-bot added the doc Issues and PRs related to Node.js documentation. label Oct 5, 2026
@aduh95 aduh95 closed this Oct 5, 2026
@aduh95 aduh95 reopened this Oct 5, 2026
@MikeMcC399

Copy link
Copy Markdown
Contributor

You may want to also consider adding a manual check instruction for releasers into https://github.com/nodejs/node/blob/main/doc/contributing/releases.md that there are no redundant pairs of commit + revert-commit in a release proposal. Just in case the instructions being updated here are overlooked or not followed. (An automated check would be better, if possible.)

I don't know how much sense this makes. As a releaser you are the best judge.

@aduh95 aduh95 added author ready PRs with CI started, the required approvals, and no outstanding review comments. commit-queue PRs queued for automated landing through the Commit Queue. labels Oct 5, 2026

@mcollina mcollina left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author ready PRs with CI started, the required approvals, and no outstanding review comments. commit-queue PRs queued for automated landing through the Commit Queue. doc Issues and PRs related to Node.js documentation.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants