Bird
Raised Fist0
Gitdevops~5 mins

git revert to undo a commit safely - Commands & Configuration

Choose your learning style10 modes available
LearnWhyDeepVisualTryChallengeProjectRecallTime

Start learning this pattern below

Jump into concepts and practice - no test required

or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
Introduction
Sometimes you make a change in your project that you want to undo without removing the history. git revert helps you undo a commit by creating a new commit that reverses the changes safely.
When you want to undo a change but keep the project history intact.
When you have already shared your commits with others and cannot rewrite history.
When you want to fix a mistake in a previous commit without deleting it.
When you want to undo a commit on the main branch without causing conflicts.
When you want to keep a clear record of what was undone and why.
Commands
This shows the last three commits with their short IDs and messages so you can choose which commit to revert.
Terminal
git log --oneline -3
Expected OutputExpected
a1b2c3d Fix typo in README 4e5f6g7 Add user login feature 8h9i0j1 Initial commit
→
--oneline - Shows each commit in a single line for easy reading
This creates a new commit that undoes the changes made in the commit with ID 4e5f6g7. It does not delete the original commit.
Terminal
git revert 4e5f6g7
Expected OutputExpected
[main 9k8l7m6] Revert "Add user login feature" 1 file changed, 10 deletions(-)
Check the last three commits again to see the new revert commit added on top.
Terminal
git log --oneline -3
Expected OutputExpected
9k8l7m6 Revert "Add user login feature" a1b2c3d Fix typo in README 4e5f6g7 Add user login feature
→
--oneline - Shows each commit in a single line for easy reading
Key Concept

If you remember nothing else from this pattern, remember: git revert safely undoes a commit by making a new commit that reverses changes without deleting history.

Common Mistakes
Using git reset to undo commits that have been shared with others.
git reset changes history and can cause conflicts for others who already have the commits.
Use git revert to undo changes safely without rewriting history.
Not specifying the correct commit ID when running git revert.
Reverting the wrong commit can undo unintended changes.
Use git log --oneline to find the exact commit ID before reverting.
Summary
Use git log --oneline to find the commit ID you want to undo.
Run git revert with the commit ID to create a new commit that reverses the changes.
Check the commit history again to confirm the revert commit was added.

Practice

(1/5)
1. What does the git revert command do in a Git repository?
easy
A. It merges two branches together.
B. It deletes the commit from the project history permanently.
C. It resets the branch to a previous commit without creating a new commit.
D. It creates a new commit that undoes the changes of a previous commit.

Solution

  1. Step 1: Understand the purpose of git revert

    git revert creates a new commit that reverses the changes made by a specified previous commit.

  2. Step 2: Compare with other commands

    Unlike git reset, it does not remove commits from history but safely adds a new commit to undo changes.

  3. Final Answer:

    It creates a new commit that undoes the changes of a previous commit -> Option D

  4. Quick Check:

    git revert = new commit undoing changes [OK]
Hint: Remember: revert adds a new commit to undo changes [OK]
Common Mistakes:
  • Confusing revert with reset which removes commits
  • Thinking revert deletes commits permanently
  • Assuming revert merges branches
2. Which of the following is the correct syntax to revert the latest commit in Git?
easy
A. git revert HEAD
B. git revert --latest
C. git revert -m HEAD
D. git revert --undo HEAD

Solution

  1. Step 1: Identify the correct command to revert the latest commit

    The latest commit is referenced by HEAD, and the correct command is git revert HEAD.

  2. Step 2: Check invalid options

    Options like --latest, -m without context, or --undo are not valid revert flags.

  3. Final Answer:

    git revert HEAD -> Option A

  4. Quick Check:

    Revert latest commit = git revert HEAD [OK]
Hint: Use HEAD to revert the latest commit safely [OK]
Common Mistakes:
  • Using invalid flags like --latest or --undo
  • Confusing revert options with reset options
  • Trying to revert without specifying a commit
3. Given the following Git commands executed in order:
git commit -m "Add feature A"
git commit -m "Fix bug B"
git revert HEAD

What will be the result of the last command?
medium
A. The commit "Fix bug B" is deleted from history.
B. The branch is reset to the commit "Add feature A" without a new commit.
C. A new commit is created that undoes the changes from "Fix bug B".
D. An error occurs because HEAD cannot be reverted.

Solution

  1. Step 1: Identify the commit pointed by HEAD

    After two commits, HEAD points to "Fix bug B" commit.

  2. Step 2: Understand what git revert HEAD does

    It creates a new commit that reverses the changes introduced by the latest commit "Fix bug B".

  3. Final Answer:

    A new commit is created that undoes the changes from "Fix bug B" -> Option C

  4. Quick Check:

    git revert HEAD = new commit undoing latest commit [OK]
Hint: Revert HEAD always creates a new undo commit [OK]
Common Mistakes:
  • Thinking revert deletes commits from history
  • Confusing revert with reset which moves HEAD
  • Assuming revert causes errors on HEAD
4. You ran git revert abc123 but got a merge conflict error. What should you do to fix this?
medium
A. Run git revert --abort to cancel the revert and try again.
B. Manually resolve the conflicts, then run git revert --continue.
C. Delete the commit abc123 and try reverting again.
D. Use git reset --hard to fix the conflict.

Solution

  1. Step 1: Understand merge conflicts during revert

    Revert can cause conflicts if changes overlap. You must resolve conflicts manually.

  2. Step 2: Continue revert after resolving conflicts

    After fixing conflicts, run git revert --continue to complete the revert commit.

  3. Final Answer:

    Manually resolve the conflicts, then run git revert --continue -> Option B

  4. Quick Check:

    Resolve conflicts + git revert --continue = fix revert conflict [OK]
Hint: Fix conflicts, then run git revert --continue [OK]
Common Mistakes:
  • Trying to delete commits to fix revert conflicts
  • Using git reset which discards changes unsafely
  • Aborting revert without resolving conflicts
5. You want to undo a commit that was pushed and shared with your team, but keep the project history intact. Which approach is safest?
hard
A. Use git revert <commit-hash> to create a new commit that undoes the changes.
B. Use git reset --hard <commit-hash> and force push to rewrite history.
C. Delete the commit from the remote repository manually.
D. Use git checkout <commit-hash> to switch to the previous commit.

Solution

  1. Step 1: Consider shared repository safety

    When commits are shared, rewriting history (reset + force push) can cause problems for others.

  2. Step 2: Use revert to safely undo changes

    git revert adds a new commit that reverses changes without rewriting history, keeping the project safe and intact.

  3. Final Answer:

    Use git revert <commit-hash> to create a new commit that undoes the changes -> Option A

  4. Quick Check:

    Revert = safe undo for shared commits [OK]
Hint: Revert to undo shared commits safely, never reset [OK]
Common Mistakes:
  • Using reset and force push on shared branches
  • Deleting commits manually from remote
  • Checking out old commits without reverting