git-revert(1)

NAME#

git-revert - Revert some existing commits

SYNOPSIS#

git revert\n [--[no-]edit] [-n] [-m <parent-number>] [-s] [-S[<keyid>]] <commit>...
\ngit revert\n (--continue | --skip | --abort | --quit)

DESCRIPTION#

Given one or more existing commits, revert the changes that the related patches introduce, and record some new commits that record them. This requires your working tree to be clean (no modifications from the HEAD commit).

Note: git revert is used to record some new commits to reverse the effect of some earlier commits (often only a faulty one). If you want to throw away all uncommitted changes in your working directory, you should see git-reset(1), particularly the --hard option. If you want to extract specific files as they were in another commit, you should see git-restore(1), specifically the --source option. Take care with these alternatives as both will discard uncommitted changes in your working directory.

See "Reset, restore and revert" in git(1) for the differences between the three commands.

OPTIONS#

<commit>...

-e, --edit

-m parent-number, --mainline parent-number

Reverting a merge commit declares that you will never want the tree changes brought in by the merge. As a result, later merges will only bring in tree changes introduced by commits that are not ancestors of the previously reverted merge. This may or may not be what you want.

See the revert-a-faulty-merge How-To[1] for more details.

--no-edit

--cleanup=<mode>

-n, --no-commit

This is useful when reverting more than one commits' effect to your index in a row.

-S[<keyid>], --gpg-sign[=<keyid>], --no-gpg-sign

-s, --signoff

--strategy=<strategy>

-X<option>, --strategy-option=<option>

--rerere-autoupdate, --no-rerere-autoupdate

--reference

SEQUENCER SUBCOMMANDS#

--continue

--skip

--quit

--abort

EXAMPLES#

git revert HEAD~3

git revert -n master~5..master~2

DISCUSSION#

While git creates a basic commit message automatically, it is strongly recommended to explain why the original commit is being reverted. In addition, repeatedly reverting reverts will result in increasingly unwieldy subject lines, for example Reapply "Reapply "<original-subject>"". Please consider rewording these to be shorter and more unique.

CONFIGURATION#

Everything below this line in this section is selectively included from the git-config(1) documentation. The content is the same as what’s found there:

revert.reference

SEE ALSO#

git-cherry-pick(1)

GIT#

Part of the git(1) suite

NOTES#

1.

revert-a-faulty-merge How-To