From 0605f01b055dd6699986bc1b80c6e65cbe3bac60 Mon Sep 17 00:00:00 2001 From: Refael Ackermann Date: Sun, 26 Nov 2017 16:43:20 -0500 Subject: [PATCH] doc: clarify fast-track of reversions MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit PR-URL: https://github.com/nodejs/node/pull/17332 Reviewed-By: James M Snell Reviewed-By: Jon Moss Reviewed-By: Ben Noordhuis Reviewed-By: Colin Ihrig Reviewed-By: Gibson Fahnestock Reviewed-By: Tobias Nießen Reviewed-By: Alexey Orlenko Reviewed-By: Gireesh Punathil Reviewed-By: Michaël Zasso Reviewed-By: Daniel Bevenius Reviewed-By: Joyee Cheung Reviewed-By: Anna Henningsen Reviewed-By: Michael Dawson --- COLLABORATOR_GUIDE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/COLLABORATOR_GUIDE.md b/COLLABORATOR_GUIDE.md index d8d0651ff53ca4..c65317dd570dcf 100644 --- a/COLLABORATOR_GUIDE.md +++ b/COLLABORATOR_GUIDE.md @@ -127,7 +127,7 @@ can be fast-tracked and may be landed after a shorter delay: * Focused changes that affect only documentation and/or the test suite. `code-and-learn` and `good-first-issue` pull requests typically fall into this category. -* Changes that revert commit(s) and/or fix regressions. +* Changes that fix regressions. When a pull request is deemed suitable to be fast-tracked, label it with `fast-track`. The pull request can be landed once 2 or more collaborators