🔀 Fix a Worktree Locking a Branch Needed Somewhere Else
`git worktree add` checks out a branch into a second working directory while registering that checkout in the main repository’s internal worktree administration, and Git enforces a rule that the SAME branch can’t be checked out in two worktrees at once. If you later try to check that branch out back in your main working directory, Git refuses with “already checked out” — even if the OTHER worktree’s folder was deleted by hand with a plain file-delete instead of through Git itself, because deleting the folder directly never told Git’s administration that the checkout ended.
🔎 The Problem
$ rm -rf ../hotfix # deleted the worktree's folder directly $ git checkout hotfix-branch fatal: 'hotfix-branch' is already checked out at '../hotfix' $ git worktree list /repo abc1234 [main] /repo/../hotfix def5678 [hotfix-branch] <- folder is gone, Git doesn't know yet
✅ Fix: Prune or Remove – Never Just Delete the Folder
- Run `git worktree list` first to see every worktree Git still believes exists, including ones whose directory was deleted by hand — it will show as present but pointing at a path that no longer exists.
- For a worktree whose folder is confirmed gone, run `git worktree prune` to have Git clean up its own administrative records, rather than trying to force the branch lock open from the other side.
- If the worktree’s directory still exists and is simply done being used, remove it properly with `git worktree remove <path>` — which also releases the branch lock — instead of deleting the folder manually.
🚨 Why This Is Dangerous
- Reaching for a forced branch delete or a forced checkout to work around the “already checked out” error, without first finding and properly removing the other worktree, can delete or detach history that worktree still had uncommitted or unpushed changes sitting on.
Deleting a worktree’s folder tells your filesystem it’s gone – it doesn’t tell Git.
