Listing worktrees in Git - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of git worktree list after adding a new worktree?

You have a main repository and you run git worktree add ../feature-branch feature. What will git worktree list show?

A

../feature-branch 123abc [detached HEAD]
.

B

../feature-branch 123abc [master]
.

C No output, command fails

D

../feature-branch 123abc [feature]
.

💡 Hint

The new worktree points to the branch you specify, not master or detached HEAD.

The git worktree add command creates a new worktree linked to the specified branch. The list shows the path, commit hash, and branch name.

🧠 Conceptual

intermediate

Which command correctly lists all worktrees with their paths and HEAD commits?

You want to see all worktrees linked to your repository with their paths and current HEAD commit hashes. Which command do you use?

A git worktree show

B git worktree list

C git worktree status

D git worktree info

💡 Hint

The command to list worktrees is simple and direct.

The git worktree list command shows all linked worktrees with their paths and HEAD commits.

❓ Troubleshoot

advanced

Why does git worktree list show only one worktree after adding multiple?

You added two worktrees using git worktree add but git worktree list shows only one. What is the most likely cause?

A The second worktree was added outside the main repository folder and not linked properly

B You need to run <code>git worktree refresh</code> to update the list

C The second worktree was added but on a detached HEAD, so it is hidden

D The <code>git worktree list</code> command only shows the main worktree by default

💡 Hint

Worktrees must be linked inside the repository's control.

Worktrees must be added inside the repository or linked properly. Adding outside without linking won't show in the list.

✅ Best Practice

advanced

What is the recommended way to clean up unused worktrees?

You have several worktrees listed by git worktree list but some are no longer needed. What is the best practice to remove them?

A Just delete the folder; Git will auto-detect and clean later

B Run <code>git worktree prune</code> without removing folders

C Use <code>git worktree remove &lt;path&gt;</code> to safely remove the worktree

D Delete the worktree folder manually and run <code>git gc</code>

💡 Hint

Git provides a command to safely remove worktrees.

Using git worktree remove removes the worktree reference and cleans up safely. Manual deletion can cause dangling references.

🔀 Workflow

expert

In what order do these commands list and clean worktrees safely?

Arrange these commands in the correct order to list all worktrees, remove an unused one, and then verify cleanup:

A 1,2,3,4

B 2,1,3,4

C 1,3,2,4

D 1,2,4,3

💡 Hint

First list, then remove, prune, and list again to confirm.

You first list worktrees to see current ones, remove the unused worktree, prune to clean references, then list again to verify removal.