{"version":"2.1.296","anchor":"git-diff-stats-now-report-per-file-status-and-renames","canonical_anchor":"git-diff-stats-now-report-per-file-status-and-renames","heading":"Per-file change counts now show whether a file was added, removed or renamed","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/git-diff-stats-now-report-per-file-status-and-renames","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Per-file change counts now show whether a file was added, removed or renamed\n\nGit change counts now record whether each file was added, removed, renamed, copied or modified, with old and new paths for renames\n\n**What**\n\nClaude Code asks git, the version control tool that tracks your files, how much each file changed. It now also requests git's `--raw` output, so each file gets a status:\n\n- added\n\n- removed\n\n- renamed\n\n- copied\n\n- modified\n\nFor renamed files, Claude Code also records the old path and the new path. A path that looks unsafe is rejected. Before, each file had only its added and removed line counts and whether it was binary.\n\n**Why**\n\nViews of your changes can now show renames and say what happened to each file, not only how many lines changed.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}