Starter
Try AI PR review.
- 2 reviewers
- Code Review
- Security Review
- 3 seats included
- 15,000 credits to start, then 5,000/mo
- About 70 reviews to start, then about 25 a month
- Unlimited repos
“Pull requests are proposals to merge code changes into a project.”[1] You push your commits to a branch, open a pull request against the branch you want them in, and the team reviews the diff before it merges.
HighKnown issue in the Code Review benchmark · caught by DeepSeek V4.1 FlashSee the graded case
GitLab calls the same thing a merge request.[2] PR is short for pull request, and the name comes from git itself: git request-pull asks a maintainer to pull your branch.[3]
The description, the timeline, the comments and the reviews.[1]
How the pull request's branch changed over time.[1]
The automated tests, builds and other validations that run on it.[1]
The diff the reviewers read.[1]
A draft pull request cannot be merged, and code owners are not asked to review it: a way to share work in progress before asking for review.[1] The pull request checklist is for when it is ready.
git switch -c fix-login-redirect
git commit -am "Fix the login redirect"
git push -u origin fix-login-redirect
gh pr create --base main --title "Fix the login redirect" --body "Returns users to the page they came from."Open one when someone else should read a change before it reaches a shared branch, or when you can't push to the repository. On a solo repository with no required reviews or checks, skip it and push to the branch directly.
On a team, collaborators push topic branches to one shared repository. On open source, anyone who can read a repository can fork it and open a pull request from the fork.[1]
Push your branch, then click Compare & pull request in the banner on GitHub, or run gh pr create in a terminal. The base branch is where you want the changes and the compare branch holds them. A title and a description tell reviewers what they are reading.[4]
Reviewers comment, approve or request changes.[5] Request changes does not block the merge unless a ruleset or branch protection rule requires reviews.[6] How to review a pull request walks through it, and the code review checklist says what to look for.
Approving signals that the changes are ready to merge.[5] An author cannot approve their own pull request. With required reviews and stale review dismissal on, a new commit that changes code dismisses an approval.[6] An approval is often written LGTM.
A merge commit keeps every commit and adds one that joins the branch. Squash and merge combines the commits into one. Rebase and merge adds each commit onto the base branch without a merge commit.[7]
Closing ends a pull request without merging it. GitHub says it fits a change that is no longer needed or that other work has replaced, and that the discussion and history stay for reference.[8]
A good pull request is small enough to serve one purpose. GitHub's docs say small, focused pull requests are easier to review and safer to merge, and they set no line limit.[9] We split the 50 open-source PRs in Martian's code review benchmark by changed lines; the median is 280 changed lines and 8 files. On average, nine AI reviewers found about half the known issues at every size up to 1,000 lines, while findings that matched no known issue rose from 1.0 per reviewer per PR at up to 300 lines to 1.8 above that.[10] IonWarp's column is Code Review, which is about average on what it finds and noisier than average past 300 lines. These PRs were picked because they hold known bugs, a finding that matched none is not always wrong, and only 3 are over 1,000 lines.
| Criterion | IonWarp | All 9 reviewers, known issues found | All 9 reviewers, findings that matched none |
|---|---|---|---|
| Up to 100 changed lines (11 PRs) | 12 of 23 known issues, 1.0 matched none per PR | 47%[10] | 1.0 per PR[10] |
| 101 to 300 changed lines (16 PRs) | 26 of 45 known issues, 1.0 matched none per PR | 52%[10] | 1.1 per PR[10] |
| 301 to 1,000 changed lines (20 PRs) | 35 of 79 known issues, 2.1 matched none per PR | 47%[10] | 1.8 per PR[10] |
| Over 1,000 changed lines (3 PRs) | 4 of 11 known issues, 3.0 matched none per PR | 30%[10] | 2.0 per PR[10] |
One workspace price with seats included. Credits pool across your team. Unlimited repos on every plan.
Try AI PR review.
Get AI PR review right from day 1.
Scale AI PR review.
Custom reviewers + credits · GitHub Enterprise · SSO/SAML + audit logs · Custom security review + SLA
A proposal to merge code changes into a project. It shows the diff, runs the checks and collects the reviews, and a maintainer merges it when it is ready.
No. Git's documentation describes git pull as a command that fetches from a remote and integrates the result into your current branch. A pull request is a feature of GitHub and similar hosts that proposes merging one branch into another and collects the review. The closest thing in Git itself is git request-pull, which only prints a request as text.
None: GitHub says pull request, GitLab says merge request. GitHub's head and base branch are GitLab's source and target branch.
A pull request marked as work in progress. It cannot be merged, and code owners are not asked to review it until it is marked ready, with the Ready for review button in the merge box.
No. GitHub does not let a pull request's author approve it; another person with access must.
It combines the pull request's commits into one commit on the base branch, so the history shows one commit per pull request.
isinstance check at line 254 tests against multiprocessing.Process which is the default context's ForkProcess class, not the SpawnProcess class created by multiprocessing.get_context('spawn'), causing the check to always be False on Linux and preventing process.kill() from being called on unhealthy workers · Code Review