review-ratio

A private badge in the GitHub header: how much you review compared to how much you ask to be reviewed.

Seed as much as you leech: code review edition. Remember private trackers? Nobody policed you. A small number next to your name did the work: your upload/download ratio. You saw it every visit, and you seeded a bit longer because of it. Nobody had to ask. review-ratio brings that number to code review. A small badge in the github.com header shows what you gave and what you asked over the last 7 days: ↑ 64,129 RP · ↓ 43,002 RP | Ratio 1.49 ↑ Upload: reviews you gave. Reviews, comments, and the code you actually went through on your teammates' pull requests. ↓ Download: reviews you asked for. The pull requests you opened, weighted by the size of what you asked others to read. Green when you give as much as you take, grey in between, amber when you've been leeching a little. Never red, never a warning, never a notification. A nudge, not a manager. • Private: only you see your ratio. No team view, no leaderboard, no manager dashboard, and no way to look up anyone else's. • No server: the extension computes everything in your browser and sends nothing anywhere except GitHub. • Read-only: it reads your pull requests and reviews and cannot write anything to GitHub. • Open formula: a page inside the extension shows how Review Points are counted, with every weight, threshold and file class. Nothing is secret, so nothing can be gamed in the dark. • Rolling 7-day window: last month's drought doesn't follow you, and a good week shows right away. Why? Pull requests wait because reviewing is invisible work. Asking costs one click; giving takes an hour. review-ratio makes both sides visible, to you only, so a moment before opening yet another PR you might pick up a teammate's first. Setup: sign in with GitHub, read-only through the review-ratio GitHub App, or paste a read-only token. An organisation owner installs the app once. Open source: https://github.com/dt-alexandre-weisser/review-ratio