Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.323 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.281 ·

.gitattributes scan says why a file touches filters

The .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

You'll notice Improvements
JSON All of v2.1.281
You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Cloud SyncArea: what it touches
ImprovementsKind: in v2.1.281,
ImprovementsSection of the release

Unclear The finding does not say whether the new reason is ever shown to the user or only kept internally.

What

A .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.

When the check flags a file, it now also says what kind of line caused it:

  • 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.
  • by: "rule" means the match came from an ordinary path rule.

The check also now skips comment lines before it looks at anything else.

Why

Each 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.

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 doubtThe finding does not say whether the new reason is ever shown to the user or only kept internally.

See this entry in the whole of v2.1.281 →

Feedback