{"version":"2.1.281","anchor":"gitattributes-scan-says-why-a-file-touches-filters","canonical_anchor":"gitattributes-scan-says-why-a-file-touches-filters","heading":".gitattributes scan says why a file touches filters","tier":"notice","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/gitattributes-scan-says-why-a-file-touches-filters","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### .gitattributes scan says why a file touches filters\n\nThe .gitattributes check now records whether a flagged file was caught by a macro or quoted line or by an ordinary rule, and skips comment lines\n\n**Unclear.** The finding does not say whether the new reason is ever shown to the user or only kept internally.\n\n**What**\n\nA `.gitattributes` file is a file in a git repository that attaches settings to file paths. One of those settings is a filter, which is a program git runs on a file's contents when it is saved or checked out. Claude Code has a check that reads this file and flags files that a filter touches.\n\nWhen the check flags a file, it now also says what kind of line caused it:\n\n- `by: \"macro_or_quoted\"` means the match came from a macro, which is a named shortcut for several settings, or from a line that uses quoted paths.\n\n- `by: \"rule\"` means the match came from an ordinary path rule.\n\nThe check also now skips comment lines before it looks at anything else.\n\n**Why**\n\nEach flagged file now carries a reason, so it is possible to tell which kind of `.gitattributes` line pulled it in. Skipping comments first means text inside a comment is not treated as a real rule.\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}