Git Revert: A Safe Way to Undo Changes in Git Repositories
What is git revert?
git revert is a Git command that safely undoes changes made by a specific commit by creating a new commit that negates the effect of the selected one.
Unlike git reset, it does not rewrite history, making it ideal for shared repositories and team workflows.
Key Characteristics of git revert
| Feature | Description |
|---|---|
| Non-destructive | Creates a new commit instead of deleting or modifying past ones |
| Collaboration-safe | Works perfectly in shared repos without history conflicts |
| Targeted Undo | You can revert one or more specific commits |
| Auditable | Keeps a traceable record of all changes, including reverts |
Basic Syntax
git revert <commit>
Replace
<commit>with the commit hash (fromgit log) or useHEADto target the most recent commit.
Common Use Cases with Examples
1. Revert the Most Recent Commit
git revert HEAD
This creates a new commit that undoes the last commit in the current branch.
2. Revert a Specific Commit by Hash
git revert abc1234
This undoes the changes introduced in the commit with hash abc1234.
3. Revert a Range of Commits
git revert oldest-commit^..newest-commit
Useful when multiple consecutive commits introduced a problem. The ^ includes the starting commit.
4. Revert a Merge Commit
git revert -m 1 merge-commit-hash
The -m flag specifies which parent is considered the “mainline” (usually 1 = main branch).
Common Options
| Option | Description |
|---|---|
--no-edit | Use the default commit message generated by Git |
-n / --no-commit | Stage the changes from the revert but don’t commit automatically |
-m <number> | Required for reverting a merge; specifies the parent branch to follow |
Example Workflow: Reverting a Bug
Step 1: Discover the buggy commit
git log --oneline
# Output:
# abc1234 Added buggy login logic
Step 2: Revert it safely
git revert abc1234
Git opens a text editor with a default revert message.
Step 3: Save and exit to create the new commit
Revert "Added buggy login logic"
Comparison: git revert vs git reset
| Feature | git revert | git reset |
|---|---|---|
| Alters commit history | No | Yes |
| Safe for shared repos | Yes | No |
| Creates new commit | Yes | No |
| Can target old commits | Yes | Yes |
| Keeps commit log trace | Yes | No |
Best Practices for Using git revert
- Use
revertfor commits that are already pushed to a shared or public repository. - Always review commit messages before confirming reverts.
- For merge commits, be sure to use
-mto indicate the mainline parent. - Use
--no-commitif you want to revert and make adjustments before finalizing the commit. - Avoid using
reseton public branches — it rewrites history and can confuse collaborators.
Summary – Git Revert
git revert is a team-friendly and non-destructive method for undoing Git changes by creating a new commit that undoes a prior one.
Key Takeaways:
- It preserves history and is safe to use on shared branches
- You can revert single or multiple commits
- It is perfect for collaborative teams and production environments
Real-World Relevance:
Whether you’re undoing a faulty deployment, cleaning up experimental features, or rolling back bugs, git revert ensures clarity, traceability, and safety in your workflow.
Git Revert – FAQ
Can I revert multiple commits at once?
Yes. Use:
git revert abc1234 def5678
Or a range:
git revert abc1234^..def5678
What does -m mean in merge reverts?
-m (mainline) tells Git which parent branch to treat as the main line. Example:
git revert -m 1 <merge-commit>
Can I cancel a revert?
Yes, by reverting the revert:
git revert <revert-commit-hash>
Does git revert delete the original commit?
No. It only reverses the changes while keeping the original commit in history.
How do I find the commit hash?
Run:
git log --oneline
Copy the short hash (e.g., abc1234) from the list.
Share Now :
