{"version":"2.1.319","anchor":"partial-clone-promisor-check-gains-a-third-argument","canonical_anchor":"partial-clone-promisor-check-gains-a-third-argument","heading":"The partial-clone check reports no promisor remotes in one more case","tier":"internal","area":"Git","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/partial-clone-promisor-check-gains-a-third-argument","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### The partial-clone check reports no promisor remotes in one more case\n\nClaude Code's check on partially downloaded git repositories now reports no promisor remotes in a new case, not only for submodules\n\n**Unclear.** What the new condition stands for, and so which repositories are affected, is not known.\n\n**What**\n\nA partial clone is a git repository downloaded without all of its history, and a promisor remote is the server git goes back to for the missing pieces. Claude Code checks for these.\n\nThat check now takes an extra condition. When the condition is not met, it reports that the repository has no promisor remotes. Before, only the submodule case (a repository nested inside another) gave that answer.\n\n**Why**\n\nThis may change when Claude Code reports that a repository relies on promisor remotes.\n\n- Area: Git\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}