What is code review? What to check in a pull request
Code review is a second engineer reading a change before it merges, to catch bugs and security holes before users hit them.
The most common miss sits outside the diff. Two AI readers independently graded 267 IonWarp findings, nearly all from 24 to 29 September 2026. Of the 17 that were real merge blockers, 12 were a test, a migration, a config value or a second read path the pull request forgot to change.
Updated
Where code review happens: the pull request
A proposed change, waiting for review
“Pull requests are proposals to merge code changes into a project.”[1] You push a branch, open one against main and request a code review under Reviewers in its sidebar;[2] the team reviews it there. What is a pull request covers forks, approvals and merge methods. Projects that work by email, such as the Linux kernel, ask for a merge with a message that git request-pull writes. We also publish a comparison of code review tools, from Gerrit to static analyzers and AI reviewers, at bestcodereviewtools.com.
Four tabs
Conversation holds the description and reviews; Commits, the branch's history; Checks, the tests and builds; Files changed, the diff the reviewer reads.[1]
A draft until it is ready
A draft cannot be merged, and code owners are not asked to review it until you mark it ready for review.[1]
Code review checklist
Read the description first
Know what the change is meant to do before you read the diff. The author's side is the pull request checklist.
Check the tests
A test covers the new behavior and would fail without the change. On a UI change, try the keyboard too.
Follow the change outside the diff
Search for the callers, tests, migrations, configs and docs of anything renamed, removed or retyped. In that read, one of our own pull requests took a release gate to 36 migrations and left a test expecting 35. Another hid a kind of run from the leaderboard and events, and the public runs endpoint kept serving it. IonWarp's reviewers raised all 17, so the sample leans toward what they look for. An AI reviewer can take this first pass: how the models scored.
Look at the failure paths
Errors are handled, never swallowed, and a retry cannot charge or send twice.
Check access and secrets
New routes check who is calling, input is validated, and no secret lands in code or logs. Security code review goes further.
Separate blocking from suggestions
Mark what must change before merge, label what is optional as a nit, and approve once it has. Code review terms lists the shorthand: LGTM, PTAL, SGTM.
Types of code review
IonWarp's column is its Code Review agent on a GitHub pull request. The last row is not a ranking: each figure was measured a different way.
| IonWarp | Pull request review | Pair programming | Formal inspection | |
|---|---|---|---|---|
| Who reads the code | IonWarp: An AI model, which reads the pull request and the code around it | Pull request review: A teammate, in a tool that shows the diff and holds the comments[3] | Pair programming: A second developer, the navigator, while the driver writes[3] | Formal inspection: Several developers, line by line, in a series of meetings[4] |
| When it happens | IonWarp: On every pull request, and again when you push a commit | Pull request review: After the change is written, before it merges[3] | Pair programming: While the code is being written[3] | Formal inspection: In multiple formal phases[4] |
| What has been measured | IonWarp: IonWarp on DeepSeek V4.1 Flash found 77 of 158 known issues on 50 benchmark pull requests. Qodo found the most, 98.[5] | Pull request review: About 15% of reviewers' comments at Microsoft indicated a possible defect, and at least 50% concerned long-term maintainability.[6] | Pair programming: In a 1999 University of Utah class experiment, pairs took about 15% more time and wrote code with about 15% fewer defects.[7] | Formal inspection: Capers Jones's analysis of over 12,000 projects put its latent defect discovery rate at 60 to 65%.[4] |
Sources
- GitHub Docs, About pull requests, read 2026-10-04.
- GitHub Docs, Requesting a pull request review, read 2026-11-08.
- GitLab, What is a code review?, read 2026-11-10.
- Wikipedia, Code review, read 2026-11-10.
- IonWarp benchmark, The code review benchmark: 50 pull requests, 158 known issues (release of 2026-10-06), read 2026-10-12.
- Czerwonka, Greiler and Tilford, Microsoft (ICSE 2015), Code Reviews Do Not Find Bugs: How the Current Code Review Best Practice Slows Us Down, read 2026-11-10.
- Cockburn and Williams (2000), The Costs and Benefits of Pair Programming, read 2026-11-10.
