{"version":"2.1.284","anchor":"git-ownership-check-now-reports-why-a-repository-was-unvetta","canonical_anchor":"git-ownership-check-now-reports-why-a-repository-was-unvetta","heading":"Git ownership errors now say what actually went wrong","tier":"notice","area":"Git","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/git-ownership-check-now-reports-why-a-repository-was-unvetta","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Git ownership errors now say what actually went wrong\n\nWhen Claude Code refuses to prune git worktrees, the message now says whether git failed, gave no answer, or the folder is owned by someone else\n\n**What**\n\nBefore running `git worktree prune`, Claude Code checks whether a repository is safe to touch, using git's `safe.directory` ownership rules. Before, any failure of this check gave the same message saying the folder was owned by another user. Now the refusal gives the real reason:\n\n- Git could not run\n\n- Git exited with an error, with the exit code shown\n\n- Git gave no answer\n\n- Git did not name the folder\n\n**Why**\n\nThe old message blamed folder ownership even when git itself had failed to run, which sent you looking in the wrong place.\n\n- Area: Git\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}