CodePulse Research

Data-Driven Engineering Insights

Original research based on millions of GitHub pull requests. Real numbers, actionable insights.

Featured Research

802,979 PRs Analyzed

2025 Engineering Benchmarks: Year in Review

What changed in how software ships—and what to watch in 2026

GitHub Archive / BigQuery | October 2025

90%

No Review

(1000+ line PRs)

71%

Self-Merged

(all PRs)

20x

Less Scrutiny

(large PRs)

38%

Longer Wait

(new contributors)

Deep Dives

3.4M

PRs Analyzed

3.4 Million PRs, One Uncomfortable Truth

Analysis of 3.4 million merged pull requests reveals 83% of large code changes ship without review. The largest public study of code review practices on GitHub.

Read article

18x

Less Scrutiny

The Rubber Stamp Problem

Large PRs receive 18x fewer review comments per line. The bigger the change, the less anyone looks.

Read article

68%

Self-Merged

The Self-Merge Reality

Two-thirds of all code on GitHub is merged by the same person who wrote it.

Read article

53%

Longer Wait

The First-Contribution Tax

New contributors wait 53% longer for their PRs to be reviewed. The onboarding tax is real.

Read article

19%

Monday Merges

Monday is Merge Day

1 in 5 PRs merge on Monday. Friday deployments? Not as common as you think.

Read article

4x

Speed Gap

The Language Speed Hierarchy

Your language choice affects how fast PRs merge. PowerShell is 4x faster than C.

Read article

83%

No Review

The 1000-Line Threshold

Once you cross 1000 lines, code review effectively stops. 83% get zero review.

Read article

62%→34%

Bot PR Decline

The Rise and Fall of Bot PRs

Bot PRs peaked at 62% in 2022 and dropped to 34% in 2024. What changed?

Read article

27%

Weekend Work

The Always-On Engineering Culture

27% of code ships on weekends. 64% of PRs happen after hours. Is your team sustainable?

Read article

50x

Variance

What Separates Elite Engineering Teams

From 0 hours to 102 hours—why cycle time varies 50x across top projects.

Read article

3h

Median Cycle

The Enterprise Benchmark: What Reviewed PRs Reveal

Global GitHub stats are misleading. Analysis of 117K PRs that actually get reviewed reveals enterprise-relevant metrics.

Read article

92%

Waiting Time

Cycle Time Decoded: Where Your PRs Spend Their Time

92% of PR cycle time is waiting for review. Breaking down the 3 phases of the PR lifecycle reveals where to focus.

Read article

10.9x

Wait Multiplier

The 10x First-Timer Penalty

First-time contributors wait 10.9x longer for review in reviewed repos. The onboarding bottleneck is worse than you think.

Read article

70%

Faster

How AI Developer Tools Ship Code

We analyzed Codex, Gemini CLI, and Claude Code. AI tool repos ship 70% faster with 6x better review engagement.

Read article

90%

No Review

The Rubber Stamp Problem 2025

90% of massive PRs ship without review in 2025—up from 83% in 2024. Large PRs get 20x less scrutiny.

Read article

71.5%

Self-Merged

The Self-Merge Reality 2025

71.5% of PRs are self-merged in 2025—up 3.45pp from 2024. In reviewed repos, it drops to 52%.

Read article

23.5%

Wed Merges

Wednesday is the New Monday

Peak merge day shifted from Monday (19%) to Wednesday (23.5%). The workweek rhythm has changed.

Read article

6x

Speed Gap

The Language Speed Hierarchy 2025

PowerShell merges 6x faster than C in 2025. 25 languages ranked by cycle time, review rate, and approval patterns.

Read article

62%→15%

Bot Decline

The Bot Collapse: Why Automation Peaked in 2022

Bot PRs dropped from 62% in 2022 to 15.5% in 2025. The automation bubble burst—here is what happened.

Read article

25%

Weekend Work

Weekend Commits = Burnout Risk

25% of code ships on weekends. 17% of reviewed PRs merge Saturday/Sunday. What your git history reveals about burnout.

Read article

About Our Research

Data Sources

Our research is based on the GitHub Archive, a project that records the public GitHub timeline. We query this data using Google BigQuery to analyze millions of pull request events.

Why Ungated?

We believe research should be accessible. All our findings are published without email gates or paywalls. If you find our data useful, consider linking back to the original study.

How to Cite

CodePulse. (2025). 3.4 Million PRs, One Uncomfortable Truth. https://codepulsehq.com/research/code-review-study-2025

Want to analyze your own team's PR data?

CodePulse connects to your GitHub and shows you these metrics for your repositories.