Git Worktrees Reference FAQs

Question 1

How do I clean up deleted worktree directories?

Accepted Answer

If you manually delete a worktree directory, you should run 'git worktree prune' to remove the stale administrative references from the main Git repository.

Question 2

How do I handle port conflicts when running multiple worktrees?

Accepted Answer

The guide recommends assigning unique ports via environment variables (e.g., PORT=3001 vs PORT=3002) for each worktree instance to prevent local server collisions.

Question 3

Why should I add .worktrees/ to my .gitignore?

Accepted Answer

Since each worktree is a full checkout located within your project structure, failing to ignore the directory would result in accidentally committing nested copies of your entire codebase into the main repository.

Question 4

What are the main benefits of using Git worktrees?

Accepted Answer

Worktrees allow you to have multiple branches checked out simultaneously in separate directories while sharing a single repository, eliminating the need to stash changes or clone the repo multiple times for parallel tasks.

Question 5

Can I use the same branch in two different worktrees?

Accepted Answer

No, Git prevents checking out the same branch in multiple worktrees simultaneously to avoid data corruption. You must create a new branch or use an existing, unassigned one for each worktree.

Git Worktrees Reference

Key Features

Use Cases

Git Worktrees Reference

Key Features

Use Cases