PR Diff Breakdown for GitHub

Breaks a GitHub pull request's line count down by file type, so an 8-line change doesn't look like 2,000.

A pull request reads +1,346 −2,371 and everyone decides to review it later. In reality the code change is 8 added and 7 removed lines, and the rest is a re-recorded test fixture. That is a five-minute review wearing a two-hour costume. PR Diff Breakdown replaces GitHub's line count with a breakdown by file type, so you can see what a pull request is actually made of before deciding when to review it: go +1.1k −8 yaml +380 −23 cue +325 −6 +1 more · 44% Click any chip for a per-file breakdown, with each file linking straight to its diff. WORKS WITH NO SETUP Files are grouped by extension out of the box. If a repository already marks generated files in its .gitattributes — the same linguist-generated attribute GitHub itself uses to collapse those diffs — they are grouped as "generated", sorted last, and shown striped. Nothing to configure. CONFIGURABLE WHEN YOU WANT IT A repository can check in .github/pr-diff-breakdown.yml to name its own categories, so everyone reviewing it sees the same numbers: version: 1 buckets: - label: cassettes icon: yaml patterns: - tests/cassettes/** You can also add personal rules in the extension's options, optionally scoped to a single organisation or repository. Your rules win over a repository's, which win over .gitattributes, which falls back to the file extension. DETAILS • No token and no sign-up. It reads the pull request's own .diff using your existing GitHub session, so private repositories and GitHub Enterprise work straight away. • No data is collected or transmitted anywhere. The only thing stored is your own configuration, in Chrome's sync storage. • The counts always add up to the number GitHub itself reports. • The tab bar keeps priority: the breakdown takes only the space left over. • Well-known file types get their own icon. Open source, MIT licensed: https://github.com/vinnymeller/github-pr-diff-breakdown