How to review a pull request on GitHub, step by step
On GitHub you read a pull request in the Files changed tab, comment on lines, and submit the review as Comment, Approve or Request changes.[1] Most real misses sit outside the diff: a test, migration, config value or second read path the change should have touched too.
The five steps below are GitHub's; the code review checklist is what to look for. To get a first pass before yours, add the IonWarp GitHub App: its Code Review agent reads every pull request when it opens and on each new push, and comments on the lines that need a fix. A person still approves the merge.
Updated
The five steps
Read the description first
Know what the change is meant to do, and which issue it closes, before you open the diff.
Open Files changed
Read one file at a time and mark each one Viewed; the header counts how many you have read.[1]
Search outside the diff
For anything renamed, removed or retyped, find its callers, tests, migrations and configs. In Keycloak #36880 the bug sat in a file the pull request never touched: it created per-client resources with no type, so a new lookup by type found none of them. On the code review benchmark DeepSeek V4.1 Flash, DeepSeek V4 Pro, Qodo and Bugbot flagged it.[2]
Comment on the line, with the fix
Name the input that breaks it and what happens, as in these real review comments. For a small fix, add a suggestion block the author can commit.[1]
Submit the review
Comment, Approve or Request changes. Request changes does not block the merge on its own; a ruleset or GitHub branch protection rule does.[1] The shorthand in comments is in code review terms: PTAL, LGTM, nit.
Sources
- GitHub Docs, Reviewing proposed changes in a pull request, read 2026-10-04.
- IonWarp benchmark, keycloak/keycloak #36880 (client permissions), graded code review findings, read 2026-10-04.
