{"version":"2.1.304","anchor":"git-remote-vetting-re-checks-consent-and-config","canonical_anchor":"git-remote-vetting-re-checks-consent-and-config","heading":"Git fetch safety check now catches config changed after it was checked","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/git-remote-vetting-re-checks-consent-and-config","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Git fetch safety check now catches config changed after it was checked\n\nClaude Code re-checks permission before retrying a git fetch and now refuses if the repository's git config changed after its safety checks\n\n**What**\n\nIn some cases Claude Code fetches from a git remote (the copy of a repository on another server) only when it is needed. Before doing so it checks the repository's settings. Before it retries such a fetch, it now checks again at several points that it is still allowed to go ahead.\n\nThere is also a new reason for refusing: the repository's git config changed after Claude Code checked it. Previously it could only refuse when the config changed while the check was still running.\n\n**Why**\n\nThis closes a gap where a repository could change its own git settings after the check had finished but before the fetch ran. If you see this refusal, the repository's git config was modified during that window.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}