{"version":"2.1.323","anchor":"git-diff-stats-can-compare-against-the-branch-merge-base","canonical_anchor":"git-diff-stats-can-compare-against-the-branch-merge-base","heading":"Change counts can now be measured against the point where your branch split off","tier":"notice","area":"Git","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/git-diff-stats-can-compare-against-the-branch-merge-base","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Change counts can now be measured against the point where your branch split off\n\nClaude Code can now count changed lines against where your branch split from its base branch, and ignores renames when counting\n\n**Unclear.** Where in Claude Code these branch-wide counts are shown is not stated.\n\n**What**\n\nClaude Code counts how many lines were added and removed in your Git repository. Before, these counts covered only your uncommitted work. They can now also be measured against the merge-base, the commit where your branch split off from its base branch, so they include everything done on the branch.\n\nThe count now runs with `--no-renames`, so a renamed file is counted as one file removed and one added. The check for new files that Git does not track yet also changed internally.\n\n**Why**\n\nThe change counts Claude Code shows may now cover your whole branch rather than only what you have not committed yet.\n\n- Area: Git\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}