Git revert multiple commits
In this article, we will see how to revert multiple commits in Git.
In Git, we may have completed many commits for some feature development, or submitted some bug fixes.
We might now decide to abandon this work. Therefore, to restore the repository to the state it was in before we made these changes, we need to revert the multiple commits that we made.
We can git revertrevert multiple commits in Git using the command.
Another way to revert multiple commits is to use git resetthe command.
We will now illustrate them with an example.
git revertRevert multiple commits in Git
using
Suppose we made multiple commits for some bug fixes.
We can see these commits in Git's log as shown below.
$ git log --oneline
17b787d bug3 fixed
1fefb57 bug2 fixed
8b3560b bug1 fixed
784065c feature1 developed
...
Now, we've decided to abandon those bug fixes and restore the repository to bug1 fixedits pre-state state.
Therefore, we can use the -d command with --no-committhe -p option git revert. The syntax of the command is git revert --no-commit <commit>.
So, to revert the three commits of the bug fix that we had done, we need to do the following.
$ git revert --no-commit 17b787d784065c
$ git revert --no-commit 1fefb57
$ git revert --no-commit 8b3560b
As a result, the repository in Git is now in bug1 fixedthe state it was in before the commit.
We sha1reverted each commit using its name.
We need to commit this state of the working tree in the Git repository as shown below.
$ git commit -m "the fixes for bugs 1 2 3 reverted"
git resetRevert multiple commits in Git
using
Suppose we have some merge commits in the repository. Then git revertthe above solution using will not work.
In this case, we need to use git resetthe command.
So, to revert multiple commits using in Git git reset, we need to do the following.
$ git reset --hard 784065c
$ git reset --soft ORIG_HEAD
$ git commit
Therefore, we use git resetthe command to revert the repository to the commit in the commit history immediately before the first bug fix, 784065c feature1 developedi.e.
So this works even if we have some merge commits.
For reprinting, please send an email to 1244347461@qq.com for approval. After obtaining the author's consent, kindly include the source as a link.
Related Articles
Push to a specific branch in Git
Publish Date：2025/04/02 Views：53 Category：Git
-
In Git, we use branches to develop independent features directly from the main workflow of the project. Since Git is considered to be the best version control system so far, we have local and remote branches in our repository for different
Solve the Git Push Everything Up-To-Date Problem
Publish Date：2025/04/02 Views：120 Category：Git
-
Git is a free, open source version control system designed to work with projects quickly and efficiently. You can make changes to your repo and push them to master branches. This article explains how to use git push the command to resolve e
Git merge development branch into feature branch
Publish Date：2025/04/02 Views：126 Category：Git
-
Creating new branches and merging them is considered to be the most powerful tool of Git. The ability of Git to create new branches and merge them into the development code is very useful for developers working in a team environment. This f
Understanding Git conflict markers
Publish Date：2025/04/02 Views：112 Category：Git
-
In this article, we will discuss git conflict markers. Understanding Git conflict markers When pulling changes from a remote repository, you may encounter merge conflicts. Merge conflict files can sometimes be confusing. A typical merge con
Selectively merge changes from different branches in Git
Publish Date：2025/04/02 Views：116 Category：Git
-
This article will discuss merging specific changes from one branch to another. As we know, when merging branches, Git merges all files without exception. You may find yourself in a scenario where you have some commits in one branch and you
Complete the merge after resolving conflicts in Git
Publish Date：2025/04/02 Views：63 Category：Git
-
This article describes the process of completing a merge after resolving merge conflicts in Git. We will go through the merge steps, resolve the conflicts, and complete the merge. Complete the merge after resolving conflicts in Git For a si
Merge the development branch into Master in Git
Publish Date：2025/04/02 Views：167 Category：Git
-
This article provides an overview of merging a development branch into the master branch. Often we find ourselves creating a branch outside of the master branch for development. Once we are happy with the changes, we can merge them into mas
Recovering a conflicting Git merge
Publish Date：2025/04/02 Views：160 Category：Git
-
This article explains the revert command when a merge conflict occurs git merge . We will also take a quick look at how to undo a git merge that was successful and has been pushed to a remote repository. Recovering a conflicting Git merge I
Git merge-base determines the most recent common ancestor of two branches
Publish Date：2025/04/02 Views：126 Category：Git
-
This article explains how we can find the most recent common ancestor commit in Git. This comes in handy when you create a branch or merge one branch into another. Without further ado, let’s get into today’s topic. Determine the most re
