Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
GitArea: what it touches
Internal ChangesKind: in v2.1.282,
Internal ChangesSection of the release
What
Git 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.
That 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:
passes --cached, so git reads the committed version rather than the working folder
passes -c core.attributesFile=/dev/null, so your personal attributes file is ignored
sets GIT_ATTR_NOSYSTEM=1, so the system-wide attributes file is ignored
The default mode still reads from the working folder as before.
Why
When 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.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhich parts of Claude Code use the new committed-only mode is not stated.
