{"version":"2.1.290","anchor":"gitattributes-handling-now-treats-any-converted-file-as-unsu","canonical_anchor":"gitattributes-handling-now-treats-any-converted-file-as-unsu","heading":"Files that git converts are now treated as unsupported","tier":"notice","area":"Git","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/gitattributes-handling-now-treats-any-converted-file-as-unsu","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Files that git converts are now treated as unsupported\n\nClaude Code now marks any file git converts through its attributes as unsupported, not only those with a filter or encoding set\n\n**Unclear.** It is not clear what Claude Code does with a file marked unsupported, or how often the no-attributes case occurs.\n\n**What**\n\nGit can be told, through attribute settings, to convert a file when it is checked out. Claude Code now treats any file git marks as converted as unsupported. Before, it did so only when a filter or a working-tree encoding was set for the file.\n\nClaude Code also now returns unsupported when no attribute information is found for a file at all.\n\n**Why**\n\nThis changes how Claude Code handles files affected by git attributes.\n\n- Area: Git\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}