{"version":"2.1.314","anchor":"bash-edit-diff-ignores-cr-only-and-converted-files","canonical_anchor":"bash-edit-diff-ignores-cr-only-and-converted-files","heading":"Changes made by Bash no longer show files that differ only in line endings","tier":"notice","area":"Bash Tool","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/bash-edit-diff-ignores-cr-only-and-converted-files","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Changes made by Bash no longer show files that differ only in line endings\n\nClaude Code's diff of files changed by Bash now ignores Windows-style line-ending differences and drops files with no real change\n\n**What**\n\nAfter Claude runs a Bash command that changes files, Claude Code shows the differences. Files whose line endings were converted, for example between Windows-style and Unix-style endings, are now checked again with git's `--ignore-cr-at-eol` option. Files with no real change left after that are dropped from the list.\n\n**Why**\n\nIn repositories that use Windows-style line endings, you should see fewer files listed as changed when only their line endings moved.\n\n- Area: Bash Tool\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}