{"version":"2.1.290","anchor":"git-config-reading-skips-unsafe-configs","canonical_anchor":"git-config-reading-skips-unsafe-configs","heading":"Claude Code now ignores git config files that fail a safety check","tier":"notice","area":"Git","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/git-config-reading-skips-unsafe-configs","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Claude Code now ignores git config files that fail a safety check\n\nWhen Claude Code reads a repository's git config file, it now returns nothing if the content fails a check, instead of always using it\n\n**Unclear.** It is not clear what content the check rejects.\n\n**What**\n\nA git repository keeps its settings in a file called `.git\/config`. Claude Code reads it for things such as the address of the remote repository (the remote origin url) and the `pushurl`, the address it pushes to.\n\nPreviously Claude Code parsed that file and always used what it found. Now every read goes through one shared step that checks the content first and returns nothing if the check flags it. This covers the remote address lookups and a new way of reading the config from the repository or from the `.git` folder.\n\n**Why**\n\nThis looks like protection against git config files written to cause harm. If Claude Code stops seeing a repository's remote address, the config file may have failed this check.\n\n- Area: Git\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}