{"version":"2.1.299","anchor":"git-config-subsection-names-are-now-parsed","canonical_anchor":"git-config-subsection-names-are-now-parsed","heading":"Git config reader now keeps names like \"origin\" in section headers","tier":"notice","area":"Git","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/git-config-subsection-names-are-now-parsed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Git config reader now keeps names like \"origin\" in section headers\n\nClaude Code now reads the quoted part of git config headers such as [remote \"origin\"] instead of skipping it\n\n**What**\n\nGit stores some settings under headers with a quoted name, such as `[remote \"origin\"]`. When Claude Code reads a git configuration file, it now keeps that quoted name and handles escape characters in it. Before, it kept only the section name, such as `remote`, and skipped the quoted part.\n\n**Why**\n\nClaude Code can now tell apart settings for different remotes or branches when it reads git configuration.\n\n- Area: Git\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}