{"version":"2.1.314","anchor":"git-numstat-parsing-fix-for-renames","canonical_anchor":"git-numstat-parsing-fix-for-renames","heading":"Per-file change counts stay correct when files are renamed","tier":"notice","area":"Git","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/git-numstat-parsing-fix-for-renames","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Per-file change counts stay correct when files are renamed\n\nLine counts for each changed file now stay correct when renamed or copied files make Git's two change lists differ in length\n\n**What**\n\nClaude Code asks Git for two lists about changed files: how many lines each one gained or lost, and which files were renamed or copied. It now matches the two lists by file path. Before, it only paired them when both lists had the same length.\n\n**Why**\n\nThe number of added and removed lines shown for each file is now correct even when some files were renamed or copied.\n\n- Area: Git\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}