Blog

Small pull requests get reviewed faster. Here’s how to keep them small

· Phillip Akuamoah-Boateng · 5 min read

A 60-line pull request gets reviewed before lunch. A 1,800-line one waits until someone has a free afternoon, and then it gets a skim and a “looks good to me”. Same team, same reviewers. Size is what changed.

Here’s why big pull requests wait, what “small” means, and a few habits that keep changes small without slowing anyone down.

Big pull requests wait, and get worse reviews

Reviewers put them off. A small change fits between meetings. A big one needs an uninterrupted hour, so it sits in the queue until that hour turns up. Meanwhile the author starts something else, and the context is gone by the time feedback lands.

Reviews get shallower as changes grow. A SmartBear study of a Cisco team found reviewers should look at no more than 200 to 400 lines at a time, and that beyond about 400 lines their ability to find defects drops (SmartBear). Google’s review guide is blunter: about 100 lines is usually a reasonable change, and 1,000 lines is usually too large (Google engineering practices).

Rework costs more. If a reviewer questions the approach on a big change, days of work are in doubt. On a small one, it’s an hour. Big branches also live longer, so they drift from main and collect merge conflicts.

Median time to first review, by pull request size
Small (up to 100 lines)
1.8h
Medium (101–400 lines)
4.5h
Large (over 400 lines)
19h
Example workspace, for illustration. Insights shows the same comparison for your repositories.

How small is small?

Count lines changed: additions plus deletions. Up to 100 lines is small, 101 to 400 is medium, and over 400 is large. Those thresholds follow the research above, and they’re the bands Nudge uses. Lines aren’t everything, though. A 300-line rename is easier to review than 40 lines of concurrency code. The real test is whether one person can review it properly in one sitting.

Habits that keep pull requests small

  • One purpose per pull request. If the description needs “and also”, it’s two pull requests.
  • Refactor first, then change behaviour. Move and rename code in one pull request that changes nothing, then make the real change in a second, small one.
  • Ship unfinished work behind a flag. Merge the parts as they’re ready, hidden from users until the feature is done. DORA lists this as a core part of working in small batches.
  • Stack dependent changes. Open the second pull request on top of the first instead of growing one branch.
  • Keep generated files and mass formatting separate. They drown out the lines that need a careful read.

“But that’s more reviews”

It is. Five 80-line pull requests mean five reviews instead of one. That only works if each review happens quickly. If a small pull request waits a day, people learn to batch changes up to make the wait worth it, and you’re back to 1,800 lines.

So small pull requests and fast first reviews go together. Each needs the other.

How Nudge helps

  • Every pull request has one accountable reviewer, who is reminded in Slack until it’s reviewed. Small pull requests don’t sit waiting for someone in the channel to pick them up.
  • Insights compares review speed by size: time to first review and cycle time for small, medium and large pull requests. It also shows median size and the share over 400 lines, with median size week by week.
  • Large pull requests are flagged while they’re open. Overview lists open pull requests over 400 lines as needing attention, and the pull request list marks them Large, so you can ask for a split before review starts.
  • Before and after. Nudge imports your last 90 days of merged pull requests, so you can see whether sizes came down once the team started working this way.

← All posts