{"version":"2.1.307","anchor":"git-config-objects-safety-checks-tightened","canonical_anchor":"git-config-objects-safety-checks-tightened","heading":"Stricter safety checks on a repository's Git folder and settings","tier":"notice","area":"Git","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/git-config-objects-safety-checks-tightened","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Stricter safety checks on a repository's Git folder and settings\n\nClaude Code now inspects every entry in .git\/objects and rejects symlinked or oversized ones, and its Git config allowlist varies by platform\n\n**What**\n\nGit keeps a project's history in a hidden `.git` folder, and its stored data in `.git\/objects`. Claude Code's safety check on that folder now looks at every entry inside it. It rejects any subfolder that is a symlink (a shortcut pointing somewhere else) or is oversized, with the message \"symlinked or oversized .git\/objects entry\". Before, it checked only the objects, `pack` and `info` folders.\n\nThe list of Git settings Claude Code accepts as safe now includes patterns that depend on your operating system. The check on the `submodule.*.update` setting now uses a shared pattern.\n\n**Why**\n\nThese are security checks on repositories. A repository that was tampered with to point Git at other files is more likely to be caught.\n\n- Area: Git\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}