{"version":"2.1.287","anchor":"git-refspec-check-distinguishes-error-from-absent","canonical_anchor":"git-refspec-check-distinguishes-error-from-absent","heading":"A git failure is no longer mistaken for missing fetch settings","tier":"notice","area":"Git","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/git-refspec-check-distinguishes-error-from-absent","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### A git failure is no longer mistaken for missing fetch settings\n\nWhen Claude Code reads a remote's fetch settings and git fails, it now treats that as an error rather than as nothing set\n\n**Unclear.** It is not clear how Claude Code acts on the new unknown result.\n\n**What**\n\nClaude Code reads your git remote's fetch settings, which say which branches git downloads from that remote. Before, any failure of that read was treated as \"not set\". Now only the case where git says the setting does not exist counts as not set. Other failures are reported as unknown.\n\n**Why**\n\nA git error no longer leads Claude Code to act as if the settings were simply missing.\n\n- Area: Git\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}