Question 1 of 6
Why would you lock a linked worktree?
The official git-worktree documentation says lock prevents automatic pruning and also prevents normal move/remove operations.
Quiz
Git Worktree Lifecycle Quiz
Check your understanding of locking, unlocking, moving, repairing, removing, and pruning Git worktrees.
6 questions
Knowledge check
Git Worktree Lifecycle Quiz
Check your understanding of locking, unlocking, moving, repairing, removing, and pruning Git worktrees.
- Stuck? Each question has an optional hint.
- Skip a hard question and review it before your results.
- Questions and answer options can shuffle between attempts.
You can retake this quiz whenever you like.
0:00
Question 2 of 6
What does `git worktree move ../old ../new` do?
The move command manages both the filesystem location and the repository-side worktree connection.
Question 3 of 6
When is `git worktree repair` appropriate?
repair reestablishes worktree administrative connections after external moves or other stale/corrupt worktree metadata.
Question 4 of 6
What normally prevents `git worktree remove` from deleting a linked worktree?
The normal remove operation requires a clean linked worktree. --force overrides that safety condition.
Question 5 of 6
What does `git worktree prune -n` provide?
The -n/--dry-run option reports what prune would remove without performing the cleanup.
Question 6 of 6
Which statement correctly distinguishes `unlock` from `repair`?
They solve different lifecycle problems: unlock changes lock state, while repair reestablishes an administrative connection after an external change.
Quiz results
0/0
Review
-
Why would you lock a linked worktree?Hint used
-
What does `git worktree move ../old ../new` do?Hint used
-
When is `git worktree repair` appropriate?Hint used
-
What normally prevents `git worktree remove` from deleting a linked worktree?Hint used
-
What does `git worktree prune -n` provide?Hint used
-
Which statement correctly distinguishes `unlock` from `repair`?Hint used