Skip to content

Large pull requests ​

A large pull request is reviewed normally. It may simply take longer to complete.

What changes as a PR growsWhat you may noticeBest response
More changed codeLonger review timeUse the dashboard to follow progress
Several concerns in one PRFindings are harder to place and act onSplit refactors from behaviour changes
More generated or fixture filesThey count towards the review capExclude generated code, fixtures and snapshots
More pushes to a large branchEach push is reviewed in fullGroup small corrections before pushing

The highest-value improvement

Write a clear title and description explaining the intent, constraints and risky areas. EasyMerge uses that pull request context when assessing the change.

It takes longer ​

Review time grows with the size of the diff. The review detail page shows how long a review took, and the dashboard shows the median across your completed reviews.

Focused pull requests get sharper reviews ​

When a change has one purpose, each finding is easier to place and act on. Smaller pull requests also finish faster.

A finding that reaches across the change carries a High impact badge on the pull request, with a Why this matters section you can expand.

Write a description ​

The pull request's title and description are read as part of the review. On a large change, a description that explains the intent is the cheapest thing you can do to improve what comes back.

Checklist for big changes ​

  • [ ] Split refactors from behaviour changes into separate pull requests.
  • [ ] Explain the intent and constraints in the pull request description.
  • [ ] Exclude generated code, fixtures and snapshots; see Excluding files.
  • [ ] Group small corrections before pushing. Each push starts a fresh review of the updated diff.