Data report"State of code review 2024" is now liveRead the full report

Index

The median engineer receives 1 review before merging a PR

TL;DR

  • The median PR is merged after one review, and the median active developer also receives one review before merging their PR.
  • Larger companies = more reviews: the median active developer at large companies (100+ committers) merges their PRs after two reviews
  • Larger PRs = more reviews: median PRs exceeding 200 lines modified receive 2 reviews before merging. Moreover, median PRs exceeding 200 lines modified at large companies receive 3 reviews before merging.

The larger the company, the more reviews an active developer’s PR receives before merging

  • We’d previously noted that company size influences the median developers’ time to merge. One reason seems to be that developers at larger companies receive more reviews per PR prior to merging compared to developers at smaller companies. (Of course, no review PRs merge the fastest)

Median reviews a developer receives before merging, by company size

The larger the PR size, the more reviews before merging

Even when normalizing for company size, we see that larger PRs are more likely to undergo more reviews before merging.

Median reviews a developer receives before merging, by company size

On this page
Git gud
"It's the first Git workflow I've used that actually feels good."
–@robboclancy
Learn more

Graphite
Git stacked on GitHub

Stacked pull requests are easier to read, easier to write, and easier to manage.
Teams that stack ship better software, faster.

Or install our CLI.
Product Screenshot 1
Product Screenshot 2