Why knowing how to undo matters in Git - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why is it important to know how to undo changes in Git?

Imagine you accidentally committed a file with sensitive information. What is the main reason knowing how to undo changes in Git is crucial?

A To permanently delete the entire project history

B To quickly fix mistakes and avoid pushing wrong changes to the shared repository

C To speed up the commit process by skipping tests

D To automatically merge conflicting branches without review

💡 Hint

Think about what happens if wrong changes get shared with others.

Knowing how to undo changes helps you fix mistakes before they affect others. It prevents errors from spreading and keeps the project clean.

💻 Command Output

intermediate

What is the output of 'git status' after undoing a commit with 'git reset --soft HEAD~1'?

You run git reset --soft HEAD~1 to undo your last commit but keep changes staged. What will git status show next?

Git

git reset --soft HEAD~1
git status

A Untracked files only

B No changes, working directory clean

C Changes to be committed: list of files from last commit

D Merge conflict message

💡 Hint

Soft reset moves HEAD back but keeps changes staged.

The soft reset removes the last commit but keeps the changes staged, so git status shows them ready to commit again.

🔀 Workflow

advanced

Which sequence correctly reverts a pushed commit without rewriting history?

You pushed a commit that introduced a bug. You want to undo it safely without rewriting history. Which command sequence is correct?

A git revert HEAD; git push

B git reset --hard HEAD~1; git push --force

C git checkout HEAD~1; git push

D git reset --soft HEAD~1; git push

💡 Hint

Think about safe ways to undo changes already shared with others.

git revert creates a new commit that undoes the changes, preserving history and avoiding problems for others.

❓ Troubleshoot

advanced

What error occurs if you try to undo a commit with 'git reset --hard' but have uncommitted changes?

You run git reset --hard HEAD~1 but Git refuses and shows an error. What is the likely cause?

A The repository is corrupted

B You are not on a branch, so reset is not allowed

C The HEAD~1 commit does not exist

D Uncommitted changes would be lost, so Git blocks the reset

💡 Hint

Think about what happens to uncommitted work during a hard reset.

A hard reset discards uncommitted changes. Git blocks it to prevent accidental data loss.

✅ Best Practice

expert

Which practice best ensures safe undoing of changes in a shared Git repository?

In a team project, what is the best practice to undo a mistake after pushing commits?

A Create a new commit with <code>git revert</code> to undo the mistake safely

B Use <code>git push --force</code> to rewrite history and fix the mistake

C Delete the remote branch and push a new one

D Reset local branch and never push again

💡 Hint

Consider how to keep history intact for your teammates.

Reverting creates a new commit that undoes changes without rewriting history, which is safer for shared work.