Git Restore, Reset, and Revert Quiz

Review

1. What does default `git restore <path>` target?

   It restores the selected tracked path in the working tree from the index by default.
2. What does `git restore --staged <path>` change by default?

   With `--staged`, restore updates the index; HEAD is the default source.
3. Which operation can change both index and working tree for selected paths without moving HEAD?

   Restore can update both local content states for selected paths while leaving the branch tip unchanged.
4. Which reset form moves the current branch tip?

   Commit-form reset sets the current branch head to the specified commit.
5. What does `git reset --soft <commit>` leave unchanged relative to the target commit?

   Soft reset moves HEAD but does not update the index or working tree.
6. What is the defining history effect of `git revert <commit>`?

   Revert records a new commit reversing the selected commit's changes.
7. A staged edit should become unstaged while the working-tree edit remains. Which operation is directly targeted at that state?

   The staged state is the index; restore --staged changes that state without updating the working tree.
8. Why is `git reset HEAD -- <path>` relevant when comparing reset and restore?

   The official reset documentation describes the path form as updating only the index and as equivalent to restore --staged.
9. Which requirement distinguishes a history-preserving reversal from local state correction?

   Revert is chosen when the reversal itself should be recorded as a new commit.
10. What should you identify before choosing among restore, reset, and revert?

    The correct choice follows the intended state transition: working tree, index, branch tip, or recorded history.