{"version":"2.1.280","anchor":"linked-worktrees-without-a-private-admin-dir-are-now-refused","canonical_anchor":"linked-worktrees-without-a-private-admin-dir-are-now-refused","heading":"Linked worktrees without a private admin dir are now refused at the git-exec layer","tier":"internal","area":"Git Worktrees","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/linked-worktrees-without-a-private-admin-dir-are-now-refused","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Linked worktrees without a private admin dir are now refused at the git-exec layer\n\nUploading a linked git worktree without a private admin dir now fails immediately instead of running git\n\n**What**\n\nThe hardened internal wrapper for running git commands during teleport bundle uploads now short-circuits to an immediate failure (empty output, exit code 126) when it detects a linked git worktree that doesn't yet have its private admin directory set up, rather than attempting to run git against it.\n\n**Why**\n\nThis avoids running git commands against a linked worktree that isn't in a state where they could succeed, failing fast and predictably instead of producing a confusing error from git itself.\n\n- Area: Git Worktrees\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}