Large pull requests
Last updated .
Does MergeSafe review very large pull requests?
Up to 2,000 hand-written changed lines MergeSafe reviews as usual; between 2,000 and 5,000 lines it asks first and reviews at 1.5 times the level’s base price; over 5,000 lines or more than 60 files it doesn’t review and suggests splitting the pull request.
| Size | What happens | Charge |
|---|---|---|
| Up to 2,000 lines | Reviewed as usual. | The level’s price. |
| 2,001 to 5,000 lines | MergeSafe comments with the price and waits. Reply @mergesafe review large to go ahead. | 1.5× the base price, add-ons as usual. Nothing until you agree. |
| Over 5,000 lines, or more than 60 files | Not reviewed. You get a comment with a ready-made prompt to split the pull request. | None. |
What counts
- Only hand-written changed lines count. Lockfiles, snapshots, vendored code, minified files and generated code don’t, as long as both the path and the contents look the part.
- Database migrations always count.
- These limits are the same for everyone; a repository can’t raise them.
Going ahead anyway
@mergesafe review large: for a paused pull request. Someone on the repository’s review list (any trusted commenter when it has none) or a repository admin can use it. The app also has a Run large review button.@mergesafe review --force: for a pull request refused as too large. A repository admin posts it after the refusal comment. It costs one review at the repository’s level.
Why not just review it?
A very large pull request asks before it is reviewed instead of getting a shallow pass, and the price is known before the review runs. Splitting it lets each part get a full review.
Related: How reviews are charged, commands.
Next: Half-price follow-ups →