From 92f3b301ab706d6254814b3f0a2689a32bbafb01 Mon Sep 17 00:00:00 2001 From: Gibson Fahnestock Date: Sat, 13 May 2017 18:12:26 +0100 Subject: [PATCH] doc: document method for reverting commits PR-URL: https://github.com/nodejs/node/pull/13015 Fixes: https://github.com/nodejs/node/issues/12979 Refs: https://github.com/nodejs/node/pull/4679#issuecomment-172421320 Reviewed-By: Colin Ihrig Reviewed-By: Rich Trott Reviewed-By: Luigi Pinca Reviewed-By: Benjamin Gruenbaum Reviewed-By: Joyee Cheung Reviewed-By: James M Snell --- COLLABORATOR_GUIDE.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/COLLABORATOR_GUIDE.md b/COLLABORATOR_GUIDE.md index b5772ee1bbff59..157925f8df8728 100644 --- a/COLLABORATOR_GUIDE.md +++ b/COLLABORATOR_GUIDE.md @@ -252,6 +252,13 @@ not can often be based on many complex factors that are not easily codified. It is also possible that the breaking commit can be labeled retroactively as a semver-major change that will not be backported to Current or LTS branches. +##### Reverting commits + +Commits are reverted with `git revert `, or `git revert ..` for +multiple commits. Commit metadata and the reason for the revert should be +appended. Commit message rules about line length and subsystem can be ignored. +A Pull Request should be raised and approved like any other change. + ### Deprecations Deprecation refers to the identification of Public APIs that should no longer