From 51c992f99bc0ec6dc1cafdc9f00defa28eead3ea Mon Sep 17 00:00:00 2001 From: Mike McCready <66998419+MikeMcC399@users.noreply.github.com> Date: Tue, 8 Sep 2026 14:04:56 +0200 Subject: [PATCH] doc: expand revert commit collaborator instructions MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Advise to add dont-land labels to commit and revert commit pairs to prevent redundant backporting. Signed-off-by: Mike McCready <66998419+MikeMcC399@users.noreply.github.com> PR-URL: https://github.com/nodejs/node/pull/65848 Reviewed-By: Luigi Pinca Reviewed-By: Gürgün Dayıoğlu --- doc/contributing/collaborator-guide.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/doc/contributing/collaborator-guide.md b/doc/contributing/collaborator-guide.md index e9dc344dcd3..2966f4dfeec 100644 --- a/doc/contributing/collaborator-guide.md +++ b/doc/contributing/collaborator-guide.md @@ -490,6 +490,10 @@ generated commit message will not have a subsystem and might violate line length rules. That is OK. Append the reason for the revert and any `Refs` or `Fixes` metadata. Raise a pull request like any other change. +Apply `dont-land-on-v?.x` labels to the revert pull request and to its +corresponding original pull request, +unless the original pull request has already been backported. + ### Introducing new modules Treat commits that introduce new core modules with extra care.