# phpman > man > git-revert(1) > **TLDR:** Create new commits which reverse the effect of earlier ones. > - Revert the most recent commit: `git revert HEAD` - Revert the 5th last commit: `git revert HEAD~4` - Revert a specific commit: `git revert {{0c01a9}}` - Revert multiple commits: `git revert {{branch_name~5}}..{{branch_name~2}}` - Don't create new commits, just change the working tree: `git revert {{-n|--no-commit}} {{0c01a9}}..{{9a1743}}` - Cancel a Git revert after a merge conflict: `git revert --abort` *Source: tldr-pages* --- [GIT-REVERT(1)](https://www.chedong.com/phpMan.php/man/GIT-REVERT/1/markdown) Git Manual [GIT-REVERT(1)](https://www.chedong.com/phpMan.php/man/GIT-REVERT/1/markdown) ## NAME git-revert - Revert some existing commits ## SYNOPSIS _git_ _revert_ [--[no-]edit] [-n] [-m parent-number] [-s] [-S[]] ... _git_ _revert_ (--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)](https://www.chedong.com/phpMan.php/man/git-reset/1/markdown), particularly the **--hard** option. If you want to extract specific files as they were in another commit, you should see [**git-restore**(1)](https://www.chedong.com/phpMan.php/man/git-restore/1/markdown), 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)](https://www.chedong.com/phpMan.php/man/git/1/markdown) for the differences between the three commands. ## OPTIONS ... Commits to revert. For a more complete list of ways to spell commit names, see [**gitrevisions**(7)](https://www.chedong.com/phpMan.php/man/gitrevisions/7/markdown). Sets of commits can also be given but no traversal is done by default, see [**git-rev-list**(1)](https://www.chedong.com/phpMan.php/man/git-rev-list/1/markdown) and its **--no-walk** option. ### -e, --edit With this option, _git_ _revert_ will let you edit the commit message prior to committing the revert. This is the default if you run the command from a terminal. -m parent-number, --mainline parent-number Usually you cannot revert a merge because you do not know which side of the merge should be considered the mainline. This option specifies the parent number (starting from 1) of the mainline and allows revert to reverse the change relative to the specified parent. 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 With this option, _git_ _revert_ will not start the commit message editor. --cleanup= This option determines how the commit message will be cleaned up before being passed on to the commit machinery. See [**git-commit**(1)](https://www.chedong.com/phpMan.php/man/git-commit/1/markdown) for more details. In particular, if the __ is given a value of **scissors**, scissors will be appended to **MERGE**___**MSG** before being passed on in the case of a conflict. ### -n, --no-commit Usually the command automatically creates some commits with commit log messages stating which commits were reverted. This flag applies the changes necessary to revert the named commits to your working tree and the index, but does not make the commits. In addition, when this option is used, your index does not have to match the HEAD commit. The revert is done against the beginning state of your index. This is useful when reverting more than one commits' effect to your index in a row. -S[], --gpg-sign[=], --no-gpg-sign GPG-sign commits. The **keyid** argument is optional and defaults to the committer identity; if specified, it must be stuck to the option without a space. **--no-gpg-sign** is useful to countermand both **commit.gpgSign** configuration variable, and earlier **--gpg-sign**. ### -s, --signoff Add a **Signed-off-by** trailer at the end of the commit message. See the signoff option in [**git-commit**(1)](https://www.chedong.com/phpMan.php/man/git-commit/1/markdown) for more information. --strategy= Use the given merge strategy. Should only be used once. See the MERGE STRATEGIES section in [**git-merge**(1)](https://www.chedong.com/phpMan.php/man/git-merge/1/markdown) for details. -X