{"version":"2.1.323","anchor":"partial-clone-worktree-fetch-hardened-and-error-text-changed","canonical_anchor":"partial-clone-worktree-fetch-hardened-and-error-text-changed","heading":"Fetching for worktrees of partial clones is locked down","tier":"soon","area":"Worktrees","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/partial-clone-worktree-fetch-hardened-and-error-text-changed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Fetching for worktrees of partial clones is locked down\n\nBehind a switch, worktree fetches in partial clones stop lazy fetching and ignore a repo's own upload-pack setting, with new error text\n\n**Unclear.** Whether the locked-down fetch is active by default is not stated.\n\n**What**\n\nA partial clone is a git repository that downloads only part of its history. When Claude Code fetches missing commits for a worktree in one, and a server-side switch is on, the fetch now:\n\n- sets `GIT_NO_LAZY_FETCH`, so git does not fetch extra objects on its own\n\n- sets `fetch.writeCommitGraph=false`\n\n- no longer uses a per-remote upload-pack setting\n\nThe error messages changed too. They can warn that the repository's config file names its own upload-pack program, which git would start. They no longer suggest checking the commit out in your main checkout.\n\n**Why**\n\nA repository's config file can no longer make Claude Code run a program of its choosing during this fetch.\n\n- Area: Worktrees\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}