How To Revert Multiple Commits in Git

Table of Contents

Introduction

Reverting multiple Git commits is a crucial process when you need to undo a sequence of changes. Whether you’re fixing errors, rolling back unwanted modifications, or restructuring your repository, Git provides several ways to revert multiple commits effectively. This guide will walk you through different methods to safely and efficiently revert multiple commits.

Why Revert Multiple Commits?

There are various scenarios where reverting multiple commits becomes necessary:

A series of commits introduced unintended bugs.
You need to roll back an entire feature.
The commits were made on the wrong branch.
You want to clean up or reorganize the commit history.

Methods to Revert Multiple Commits

1. Reverting Commits Individually

The git revert command allows you to undo changes while maintaining commit history. This method is useful when you want to selectively revert commits without modifying previous commits.

Steps:

Step 1: Identify the commits you want to revert using:

git log --oneline

Step 2: Revert each commit individually:

git revert <commit-hash1> <commit-hash2> ... <commit-hashN>

Step 3: Push the new commits to the remote repository:

git push origin <branch-name>

This approach is useful when you need to revert multiple commits while keeping a clear history.

2. Reverting a Range of Commits

If you need to revert a sequence of commits, you can automate the process using a script. While Git does not provide a built-in command to revert multiple commits in one step, a loop can achieve the same result.

Steps:

Step 1: Identify the start and end commit hashes using:

git log --oneline

Step 2: Use a loop to revert the commits:

for commit in $(git rev-list <start-commit>..<end-commit>); do git revert $commit; done

Step 3: Push the reverted commits:

git push origin <branch-name>

This method is efficient when reverting multiple consecutive commits without manually specifying each commit.

3. Resetting to a Previous Commit

The git reset command moves the HEAD pointer back to an earlier commit, effectively erasing newer commits from history. Use this with caution, as it modifies commit history.

Warning:

Force pushing (git push --force) can overwrite remote changes, potentially disrupting other developers’ work. Ensure you coordinate with your team before performing a reset.

Steps:

Step 1: Find the commit hash to which you want to reset:

git log --oneline

Step 2: Perform a hard reset:

git reset --hard <commit-hash>

Step 3: Force push to the remote repository:

git push --force origin <branch-name>

Use this method when you want to completely erase recent commits.

4. Interactive Rebase

For more complex scenarios, git rebase in interactive mode allows you to modify, reorder, or squash commits before finalizing changes.

Steps:

Step 1: Start an interactive rebase for the last few commits:

git rebase -i HEAD~<number-of-commits>

Step 2: In the interactive rebase interface, specify actions like:

pick – Keep commit as is.
reword – Change commit message.
edit – Modify commit.
squash – Merge commit with previous one.
drop – Remove commit.

Step 3: Complete the rebase and force push:

git push --force origin <branch-name>

Interactive rebasing is ideal for restructuring commit history while maintaining meaningful changes.