Git Removing and Moving Tracked Files Quiz

Review

1. What does ordinary `git rm file.txt` update before a commit?

   Ordinary `git rm` removes the file from the working tree and the index.
2. When does a `git rm` deletion become part of repository history?

   The deletion is staged by `git rm`; a commit records it in history.
3. What does `git rm --cached file.txt` leave behind?

   `--cached` removes the path from the index while leaving the working-tree file in place.
4. Why does `git rm -r docs` use `-r`?

   The directory form requires `-r` for recursive removal.
5. Why can `git rm` refuse a modified tracked file?

   The default safety check protects working-tree or staged content that would otherwise be lost.
6. What does successful `git mv old.txt new.txt` update immediately?

   `git mv` moves the path and updates the index; the change still needs a commit.
7. What records a move in repository history?

   The staged move becomes historical only when a commit records the index state.
8. Which model is most precise for teaching a committed rename?

   Git stores snapshots and paths; rename presentation is derived from comparing changes rather than being a separate history object.
9. After committing a removal and move, what should a clean working tree report?

   Once the staged path changes are committed and nothing else changed, the working tree is clean.
10. Which lesson boundary is correct?

    The path operations update the working tree/index; committing is the history transition.