git reset soft vs mixed vs hard - Practice Questions

Challenge - 5 Problems

🧠 Conceptual

intermediate

Difference between git reset --soft and git reset --mixed

After running git reset --soft HEAD~1, what happens to the changes from the last commit?

A The changes remain staged in the index, ready to commit again.

B The changes are unstaged and moved to the working directory.

C The changes are discarded completely from the working directory and index.

D The changes are saved in a new branch automatically.

💡 Hint

Think about what --soft means for the staging area (index).

git reset --soft moves the HEAD pointer but keeps all changes staged in the index. This means you can recommit them immediately.

🧠 Conceptual

intermediate

Effect of git reset --hard on working directory

What is the effect of running git reset --hard HEAD~1 on your working directory?

A It creates a new commit undoing the last commit.

B It resets HEAD but keeps changes staged in the index.

C It resets HEAD and unstages changes but keeps them in the working directory.

D It resets HEAD and discards all changes in the working directory and index to match the previous commit.

💡 Hint

Consider what --hard means for both index and working directory.

git reset --hard resets HEAD and makes both the index and working directory match the specified commit, discarding all changes.

💻 Command Output

advanced

Output after git reset --mixed

Given a repository with one commit and some changes staged and unstaged, what is the state of the index and working directory after running git reset --mixed HEAD~1?

A HEAD moves back one commit, index is reset to that commit, unstaged changes remain in working directory.

B HEAD moves back one commit, changes remain staged in index, working directory unchanged.

C HEAD moves back one commit, all changes discarded from index and working directory.

D HEAD moves back one commit, changes are saved in stash automatically.

💡 Hint

Remember --mixed resets the index but not the working directory.

git reset --mixed moves HEAD and resets the index to match that commit, but leaves working directory changes unstaged.

❓ Troubleshoot

advanced

Recovering a lost commit after git reset --hard

You accidentally ran git reset --hard HEAD~1 and lost the last commit. Which command can help you recover it?

A <code>git stash pop</code> to recover changes automatically.

B <code>git revert HEAD~1</code> to undo the reset.

C <code>git reflog</code> to find the previous HEAD and then <code>git reset</code> to restore.

D <code>git checkout -- .</code> to restore all files.

💡 Hint

Think about how Git tracks HEAD movements even after resets.

git reflog shows recent HEAD positions. You can reset back to a previous HEAD to recover lost commits.

✅ Best Practice

expert

Choosing the right git reset mode for undoing commits safely

You want to undo the last commit but keep your changes safe and ready to edit before recommitting. Which git reset mode should you use?

A <code>git reset --hard HEAD~1</code> to discard changes and reset everything.

B <code>git reset --soft HEAD~1</code> to keep changes staged for editing.

C <code>git revert HEAD</code> to create a new commit undoing the last one.

D <code>git reset --mixed HEAD~1</code> to unstage changes but keep them in working directory.

💡 Hint

Consider which reset mode keeps changes staged for easy recommit.

git reset --soft moves HEAD but keeps changes staged, so you can edit and recommit easily without losing work.