{"version":"2.1.301","anchor":"lazy-fetch-git-vetting-can-target-a-named-remote","canonical_anchor":"lazy-fetch-git-vetting-can-target-a-named-remote","heading":"Git config check for on-demand fetching can now target a named remote","tier":"internal","area":"Git","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/lazy-fetch-git-vetting-can-target-a-named-remote","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Git config check for on-demand fetching can now target a named remote\n\nClaude Code's safety check on git configuration before on-demand fetches can now check a specific named remote\n\n**What**\n\nIn a partial git clone, some data is fetched only when it is needed (a \"lazy fetch\"). Claude Code checks the repository's git configuration before allowing this. That check can now be pointed at a specific named remote, a remote being a server git fetches from.\n\nWhen it is:\n\n- It looks at that remote and at any `remotes.<name>` group setting.\n\n- It fails with `named_remote_without_url` unless the repository's own config sets `remote.<name>.url`.\n\n- It sets `GIT_NO_LAZY_FETCH=1` and reports \"GIT_NO_LAZY_FETCH is set, which switches this command off too\".\n\nBefore, the check only ever looked at the remote that supplies missing data in a partial clone.\n\n**Why**\n\nIt extends or tightens the safety checks Claude Code places around git fetching.\n\n- Area: Git\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}