Why Removing worktrees in Git? - Purpose & Use Cases

The Big Idea

Discover how a simple git command can save you from messy project folders and hidden errors!

The Scenario

Imagine you have multiple copies of your project checked out in different folders to work on various features. When a feature is done, you want to clean up by deleting those extra folders manually.

The Problem

Manually deleting folders can be risky and confusing. You might delete the wrong folder or leave behind hidden git data, causing errors later. It's slow and easy to make mistakes.

The Solution

Using git's worktree removal commands safely cleans up these extra checkouts. It removes the link between the main repo and the worktree, and deletes the folder properly, avoiding leftover data and confusion.

Before vs After

✗ Before

rm -rf feature-folder

✓ After

git worktree remove feature-folder

What It Enables

You can manage multiple project copies confidently and cleanly, keeping your workspace organized without fear of breaking your main repository.

Real Life Example

A developer finishes a bug fix in a separate worktree and wants to delete it. Using git worktree remove safely removes the worktree and frees up space without risking the main project.

Key Takeaways

Manual folder deletion risks leftover git data and errors.

git worktree remove safely cleans up extra checkouts.

It keeps your project organized and error-free.

Practice

1. What does the command git worktree remove <path> do?

easy

A. Deletes the specified extra worktree folder and unregisters it from Git.

B. Creates a new worktree at the specified path.

C. Lists all existing worktrees in the repository.

D. Resets the current branch to the specified commit.

Solution

1. Step 1: Understand the command purpose

   The command git worktree remove <path> is used to remove an extra worktree folder from your Git repository.

2. Step 2: Effect of the command

   It deletes the worktree folder at the given path and unregisters it from Git, keeping the project clean.

3. Final Answer:

   Deletes the specified extra worktree folder and unregisters it from Git. -> Option A

4. Quick Check:

   Remove worktree = Delete folder + unregister [OK]

Hint: Remove worktree means delete folder and unregister it [OK]

Common Mistakes:

• Confusing remove with create or list commands
• Thinking it resets branches
• Assuming it only unregisters without deleting folder

2. Which of the following is the correct syntax to remove a worktree located at ./feature-branch?

easy

A. git worktree remove ./feature-branch

B. git worktree rm ./feature-branch

C. git remove worktree ./feature-branch

D. git worktree delete ./feature-branch

Solution

1. Step 1: Recall correct command syntax

   The correct command to remove a worktree is git worktree remove <path>.

2. Step 2: Match the syntax with options

   git worktree remove ./feature-branch matches the correct syntax exactly: git worktree remove ./feature-branch.

3. Final Answer:

   git worktree remove ./feature-branch -> Option A

4. Quick Check:

   Remove worktree syntax = git worktree remove [OK]

Hint: Use 'git worktree remove' followed by path [OK]

Common Mistakes:

• Using 'delete' instead of 'remove'
• Swapping command order like 'git remove worktree'
• Using shorthand 'rm' which is invalid here

3. Given you have a worktree at ./dev, what will be the output of running git worktree list after git worktree remove ./dev?

medium

A. The list will still show ./dev but marked as removed.

B. The list will no longer show the ./dev worktree.

C. The command will fail with an error about ./dev.

D. The list will show ./dev and all other worktrees unchanged.

Solution

1. Step 1: Understand what 'git worktree remove' does

   It deletes the worktree folder and unregisters it from Git, so it is no longer tracked.

2. Step 2: Effect on 'git worktree list'

   After removal, the worktree at ./dev will not appear in the list anymore.

3. Final Answer:

   The list will no longer show the ./dev worktree. -> Option B

4. Quick Check:

   Remove worktree means it disappears from list [OK]

Hint: Removed worktrees vanish from 'git worktree list' output [OK]

Common Mistakes:

• Expecting removed worktree to still appear in list
• Thinking it shows as 'removed' but still listed
• Assuming command errors out after removal

4. You tried to remove a worktree with git worktree remove ./test but got an error saying the path is not a worktree. What is the likely cause?

medium

A. The repository is corrupted and needs reinitialization.

B. You need to use git worktree delete instead of remove.

C. You must be on the main branch to remove any worktree.

D. The path ./test does not exist or is not registered as a worktree.

Solution

1. Step 1: Analyze the error message

   The error says the path is not a worktree, meaning Git does not recognize it as one.

2. Step 2: Identify common causes

   This usually happens if the path does not exist or was never added as a worktree.

3. Final Answer:

   The path ./test does not exist or is not registered as a worktree. -> Option D

4. Quick Check:

   Path must exist and be registered to remove [OK]

Hint: Check path exists and is registered worktree before removing [OK]

Common Mistakes:

• Using wrong command like 'delete' instead of 'remove'
• Assuming branch affects removal
• Thinking repo corruption causes this error

5. You have multiple worktrees: ./feature1, ./feature2, and ./feature3. You want to remove ./feature2 but keep its changes saved. What is the best approach?

hard

A. Run git worktree remove ./feature2 without saving changes; Git saves them automatically.

B. Directly delete the ./feature2 folder without Git commands.

C. Commit or stash changes in ./feature2, then run git worktree remove ./feature2.

D. Switch to main branch and delete ./feature2 folder manually.

Solution

1. Step 1: Preserve changes before removal

   To keep changes in a worktree, you must commit or stash them before removing the worktree.

2. Step 2: Remove the worktree properly

   After saving changes, use git worktree remove ./feature2 to safely remove the worktree folder and unregister it.

3. Final Answer:

   Commit or stash changes in ./feature2, then run git worktree remove ./feature2. -> Option C

4. Quick Check:

   Save changes first, then remove worktree [OK]

Hint: Save changes (commit/stash) before removing worktree [OK]

Common Mistakes:

• Deleting folder manually causing data loss
• Assuming Git auto-saves changes on remove
• Removing without saving changes first