{"version":"2.1.290","anchor":"new-bash-git-checkout-scan-for-tracked-files-replaced-by-non","canonical_anchor":"new-bash-git-checkout-scan-for-tracked-files-replaced-by-non","heading":"A check for tracked git files replaced in the working folder","tier":"internal","area":"Git","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/new-bash-git-checkout-scan-for-tracked-files-replaced-by-non","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### A check for tracked git files replaced in the working folder\n\nClaude Code can now scan the current git checkout for tracked files that were replaced, using `git diff-index` and `git ls-files`\n\n**Unclear.** Where Claude Code uses this check and what turns it on is not settled.\n\n**What**\n\nClaude Code has a new check that looks at the git repository in the current folder. It runs `git diff-index` and `git ls-files`, looks at each file git is tracking, and reports the ones that have been replaced on disk. It gives up with a reason when, for example, it finds no `.git` folder in the current folder or a tracked path leads outside the checkout.\n\n**Why**\n\nIt appears to be a safety check around files under git's control.\n\n- Area: Git\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}