{"version":"2.1.301","anchor":"git-partial-clone-lane-can-contact-a-named-remote-fetchesfr","canonical_anchor":"git-partial-clone-lane-can-contact-a-named-remote-fetchesfr","heading":"Git checkouts can now fetch from a named remote with strict checks","tier":"internal","area":"Git","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/git-partial-clone-lane-can-contact-a-named-remote-fetchesfr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Git checkouts can now fetch from a named remote with strict checks\n\nWhen building a working copy from a partial git clone, Claude Code can now contact a named remote after checking its name and command\n\n**What**\n\nA partial clone is a copy of a git repository that downloads files only when they are needed. When Claude Code builds a working copy from one, it can now contact a named remote (another copy of the repository, usually on a server), not only the one the clone was made from.\n\nBefore doing so it checks that:\n\n- the remote name is a plain name that begins with a letter or a digit\n\n- the git command is one of a small set of allowed fetch or list forms\n\nIf a check fails, Claude Code reports that the remote was not contacted.\n\n**Why**\n\nThis tightens how Claude Code talks to git servers while preparing a working copy.\n\n- Area: Git\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}