{"version":"2.1.274","anchor":"worktree-removal-failure-reason-nested-repositoriesneste","canonical_anchor":"worktree-removal-failure-reason-nested-repositoriesneste","heading":"Worktree removal failure reason \"nested_repositories\"\/\"nested_unverified\" merged into a single \"submodule\" case","tier":"notice","area":"Git Worktrees","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/worktree-removal-failure-reason-nested-repositoriesneste","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Worktree removal failure reason \"nested_repositories\"\/\"nested_unverified\" merged into a single \"submodule\" case\n\nTwo separate nested-repository worktree-removal errors were merged into one \"submodule\" case with clearer wording\n\n**What**\n\nWhen Claude Code refuses to remove a git worktree because of nested repositories, it used to report two separate reasons internally (`nested_repositories` and `nested_unverified`). These are now merged into a single \"submodule\" case, with wording that tells apart a worktree holding a separate git repository, which should be moved or deleted, from a submodule whose state can't be verified, which needs a manual check.\n\n**Why**\n\nThis gives clearer, more consistent guidance when a worktree removal is blocked by nested repository content, telling the user directly whether they need to move or delete something versus check it manually.\n\n- Area: Git Worktrees\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}