Recovering from hard reset in Git - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of git reflog after a hard reset?

You ran git reset --hard HEAD~2 and want to see the previous commit references to recover lost work. What does git reflog show?

Git

git reflog

A A list of all branches but no commit hashes

B An empty list because hard reset deletes history

C Only the current commit hash with no previous entries

D A list of recent HEAD positions including the commit before the hard reset

💡 Hint

Think about how Git tracks HEAD movements even after resets.

git reflog records all movements of HEAD, including resets. This lets you find commits lost after a hard reset.

🔀 Workflow

intermediate

Which command sequence recovers a commit lost after a hard reset?

You accidentally ran git reset --hard HEAD~1 and want to restore the lost commit. Which sequence correctly recovers it?

A git branch; git merge origin/main

B git reflog; git checkout <commit-hash-from-reflog>

C git log; git revert HEAD~1

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

💡 Hint

Use the command that shows recent HEAD changes and then checkout the lost commit.

git reflog shows lost commits. Checking out the commit hash from reflog recovers it.

❓ Troubleshoot

advanced

Why does git reset --hard sometimes seem to lose commits permanently?

After running git reset --hard, you cannot find your previous commits in git log. What is the reason?

A The commits are still in reflog but not in the current branch history

B The commits are deleted from the repository permanently

C The commits are moved to a new branch automatically

D The commits are archived in a hidden folder

💡 Hint

Think about how Git stores commit references separately from branch pointers.

Hard reset moves the branch pointer but reflog keeps track of previous HEAD positions, so commits are not deleted immediately.

🧠 Conceptual

advanced

What is the role of git reflog in recovering from a hard reset?

Explain why git reflog is essential for recovering commits after a hard reset.

A It merges branches after a reset

B It creates backups of your repository automatically

C It records all changes to HEAD, allowing you to find lost commits

D It permanently deletes commits after reset

💡 Hint

Consider what information reflog stores about HEAD.

git reflog tracks every change to HEAD, so even if commits are no longer on a branch, you can find their hashes here.

✅ Best Practice

expert

What is the safest way to avoid losing work when using git reset --hard?

Before running git reset --hard, which practice best protects your work from accidental loss?

A Create a temporary branch pointing to the current commit

B Run <code>git clean -fd</code> to remove untracked files

C Use <code>git stash</code> and then delete the stash immediately

D Delete the .git folder to reset the repository

💡 Hint

Think about how to save your current state safely before resetting.

Creating a temporary branch saves your current commit reference, so you can return to it if needed after a hard reset.