Engineering teams already on GitHub (most modern teams) who want the rational default review surface without a second per-seat invoice. Particularly strong for teams under 200 engineers and for any team where review depth is satisfied by the GitHub native model.
Teams that need stacked PRs (Graphite better), teams that need strict reviewer-state tracking (Reviewable better), regulated buyers needing fully self-hosted review (GitHub Enterprise Server works but is a heavier procurement), or teams not on GitHub.
Is GitHub Pull Requests a trustworthy vendor?
- 2018-06-04Microsoft acquired GitHub for $7.5BSustained product investment since the acquisition; review surface materially improved through 2018-2026.
- 2023-07-19Merge queue launched (Enterprise Cloud)Native merge-queue feature reduces dependence on Mergify for many GitHub Enterprise buyers.
- 2024-09-17Copilot review summaries launchedAI review surface added; useful but still nascent next to dedicated AI tools like CodeRabbit or Greptile.
What 2,100 reviews actually say
Synthesized from G2, Capterra, Reddit, Trustpilot. Patterns >15% prevalence shown.
Praise patterns
- Free at every paid GitHub tier (no second invoice)87% →
- Deepest CI plus status-check integration78% →
- Code owners, branch protection, required reviewers71% →
- Suggested changes for inline reviewer-proposed edits64% →
Complaint patterns
- No native stacked-PR workflow51% →
- Reviewer-state model less strict than Reviewable47% →
- Merge queue gated to Enterprise Cloud tier41% →
- Copilot review summaries still nascent38% ↑
What buyers actually pay
612 anonymized deal disclosures · last updated 2026-05-01
| Company size | Median annual |
|---|---|
| Individual / Free | $0 |
| 10 to 50 users (Team) | $480 |
| 50 to 500 users (Enterprise Cloud) | $12,600 |
| 500+ users (Enterprise Cloud) | $126,000 |
Auto-verified certifications
Editorial: Strengths
- Free at every paid GitHub tier (no second invoice)
- Deepest CI plus status-check integration of any review tool
- Code owners, branch protection, required reviewers built in
- Suggested changes for inline reviewer-proposed edits
- Draft PRs for in-progress work
- Merge queue at GitHub Enterprise Cloud (2023)
- Copilot review summaries (2024) for orientation on large PRs
- Full Microsoft investment since the 2018 acquisition
Editorial: Weaknesses
- No native stacked-PR workflow (Graphite needed for that)
- Reviewer-state model less strict than Reviewable
- Merge queue gated to GitHub Enterprise Cloud tier
- Copilot review summaries still nascent next to CodeRabbit or Greptile
- Per-file disposition tracking weaker than dedicated tools
- Large PR diffs can load slowly compared to Graphite
Key features & integrations
- +Pull request review with inline comments and suggestions
- +Code owners and CODEOWNERS file
- +Branch protection rules with required reviewers
- +Status checks from CI integration
- +Draft PRs for in-progress work
- +Suggested changes for inline reviewer-proposed edits
- +Merge queue at Enterprise Cloud tier
- +Copilot review summaries (2024)
- +SAML SSO, SCIM, audit log at Enterprise
- +REST API, GraphQL API, and webhooks
Read our full ranking of Code Review Software
GitHub Pull Requests ranks #6 in our editorial review of 10 code review software platforms. The deep-dive covers methodology, comparison tables, decision matrix, migration scoring, and FAQs.
Read the full rankingClosest alternatives in Code Review Software
Contribute your verified deal price
Pricing in B2B software is opaque because vendors want it that way. Verified buyer prices fix that, anonymously. Share what you actually paid for GitHub Pull Requests; we’ll add it to the verified pricing dataset on this page (with company size band only, no identifying details).
Submit anonymously