{"version":"2.1.287","anchor":"git-lazy-fetch-error-explains-disallowed-transports","canonical_anchor":"git-lazy-fetch-error-explains-disallowed-transports","heading":"Clearer error when git can't fetch missing files over a blocked connection type","tier":"notice","area":"Git","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/git-lazy-fetch-error-explains-disallowed-transports","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Clearer error when git can't fetch missing files over a blocked connection type\n\nWhen a partial clone's on-demand fetch fails because the connection type isn't allowed, the error now explains why and names the address\n\n**What**\n\nA partial clone is a git repository downloaded without all of its file contents. Git fetches the missing pieces on demand later, which is called a lazy fetch. Git also limits which connection types, such as HTTPS or SSH, it may use.\n\nWhen a lazy fetch fails because the connection type is not allowed, Claude Code's error message now says these things:\n\n- Nothing was fetched.\n\n- A lazy fetch only runs over the allowed connection types.\n\n- The address git tried to fetch the missing pieces from.\n\n- A hint about `insteadOf` rules, which are git settings that rewrite one address into another.\n\nBefore, the message only added a hint about the `http.extraHeader` setting. Claude Code runs this git command with `LC_ALL=C` so it can recognise the error.\n\n**Why**\n\nIf you work in a repository with an unusual git setup, the error now points at the real cause instead of an unrelated setting.\n\n- Area: Git\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}