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.

Practice

1. What does the command git worktree list do?

easy

A. Deletes all existing worktrees

B. Shows the commit history of the current branch

C. Creates a new worktree

D. Shows all the linked worktrees with their paths and branches

Solution

1. Step 1: Understand the purpose of git worktree list

   This command lists all worktrees connected to the repository, showing their folder paths and branches.

2. Step 2: Compare with other options

   Options A and C describe deleting or creating worktrees, which are done by different commands. Shows the commit history of the current branch shows commit history, unrelated to worktrees.

3. Final Answer:

   Shows all the linked worktrees with their paths and branches -> Option D

4. Quick Check:

   List worktrees = B [OK]

Hint: Remember: 'list' shows all worktrees and their details [OK]

Common Mistakes:

• Confusing 'list' with 'add' or 'remove' commands
• Thinking it shows commit history
• Assuming it deletes worktrees

2. Which of the following is the correct syntax to list all git worktrees?

easy

A. git worktree show

B. git worktree ls

C. git worktree list

D. git worktree status

Solution

1. Step 1: Recall the exact command for listing worktrees

   The correct command is git worktree list to display all worktrees.

2. Step 2: Verify other options

   Options A, B, and D are invalid or do not exist in git worktree commands.

3. Final Answer:

   git worktree list -> Option C

4. Quick Check:

   Correct syntax for listing = C [OK]

Hint: Use full command 'git worktree list' to avoid errors [OK]

Common Mistakes:

• Using 'show' or 'status' instead of 'list'
• Shortening 'list' to 'ls' which is invalid
• Confusing with other git commands

3. Given the output of git worktree list below, what branch is checked out in the worktree at /projects/myrepo/feature?

/projects/myrepo  123abc [main]
/projects/myrepo/feature  456def [feature-branch]

medium

A. main

B. feature-branch

C. 123abc

D. 456def

Solution

1. Step 1: Identify the worktree path in the output

   The path /projects/myrepo/feature corresponds to the second line in the output.

2. Step 2: Read the branch name in brackets

   The branch checked out there is feature-branch, shown in square brackets.

3. Final Answer:

   feature-branch -> Option B

4. Quick Check:

   Branch at /feature = feature-branch [OK]

Hint: Branch name is always in brackets after path [OK]

Common Mistakes:

• Confusing commit hashes with branch names
• Picking the wrong line for the path
• Ignoring the brackets around branch names

4. You ran git worktree list but got an error: fatal: 'worktree' is not a git command. What is the most likely cause?

medium

A. Your git version is too old and does not support worktrees

B. You typed 'worktree' instead of 'worktrees'

C. You are not inside a git repository

D. You need to initialize worktrees with a special command first

Solution

1. Step 1: Understand the error message

   The error means git does not recognize the 'worktree' command, likely due to version.

2. Step 2: Check git version support

   Worktrees were introduced in git 2.5+. Older versions lack this command.

3. Final Answer:

   Your git version is too old and does not support worktrees -> Option A

4. Quick Check:

   Unsupported git version = A [OK]

Hint: Check git version if 'worktree' command not found [OK]

Common Mistakes:

• Assuming typo in command name
• Thinking worktrees need special init
• Not verifying git version

5. You have multiple worktrees for your project. You want to list all worktrees and filter only those on the branch named 'release'. Which command combination will achieve this?

hard

A. git worktree list | grep release

B. git worktree list --branch release

C. git worktree show release

D. git worktree list --filter=branch=release

Solution

1. Step 1: Understand git worktree list filtering options

   Git worktree list does not have built-in branch filtering options like --branch or --filter.

2. Step 2: Use shell tools to filter output

   Using grep release after listing worktrees filters lines containing 'release', showing only those branches.

3. Final Answer:

   git worktree list | grep release -> Option A

4. Quick Check:

   Filter branches by grep after list = D [OK]

Hint: Use shell grep to filter worktree list output by branch [OK]

Common Mistakes:

• Assuming git worktree list supports --branch or --filter
• Using 'show' instead of 'list'
• Expecting git to filter output internally