{"version":"2.1.282","anchor":"git-check-attr-can-now-answer-from-the-index-ignoring-user","canonical_anchor":"git-check-attr-can-now-answer-from-the-index-ignoring-user","heading":"Git attribute lookups can now ignore personal and system attribute files","tier":"internal","area":"Git","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/git-check-attr-can-now-answer-from-the-index-ignoring-user","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Git attribute lookups can now ignore personal and system attribute files\n\nClaude Code's git attribute check can now read only committed .gitattributes files, ignoring your personal and system-wide attribute settings\n\n**Unclear.** Which parts of Claude Code use the new committed-only mode is not stated.\n\n**What**\n\nGit lets a project label files with attributes, for example marking some files as generated, using files named `.gitattributes`. Claude Code asks git for these labels with the `git check-attr` command.\n\nThat lookup previously always read attributes from the files on disk in your working folder, using your normal git settings. It can now also run in a mode that uses only the committed `.gitattributes` files. In that mode it:\n\n- passes `--cached`, so git reads the committed version rather than the working folder\n\n- passes `-c core.attributesFile=\/dev\/null`, so your personal attributes file is ignored\n\n- sets `GIT_ATTR_NOSYSTEM=1`, so the system-wide attributes file is ignored\n\nThe default mode still reads from the working folder as before.\n\n**Why**\n\nWhen Claude Code uses the new mode, the answer depends only on what the project has committed. Your own or your machine's git attribute settings cannot change which files an attribute applies to.\n\n- Area: Git\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}