How GitHub code review works
On GitHub, code review happens on pull requests: authors propose a diff, reviewers leave comments, and someone approves or requests changes before merge. CodeCritic adds an AI first pass on that same diff - structured findings grouped by severity so humans spend time on judgment, not repetitive scanning.
A review has three outcomes, and they mean different things to the author. Comment leaves feedback without blocking anything. Request changes blocks the merge until the author pushes fixes and the reviewer re-reviews. Approve clears a required-review rule - branch protection decides whether the approval survives later commits. Line comments anchor to exact diff lines; the review summary is the place for the overall verdict.
Two repo settings do most of the enforcement work. CODEOWNERS maps paths to required reviewers, so an auth change automatically asks the auth owners instead of hoping the right person notices. Branch protection turns conventions into gates: required reviews, required status checks, and whether stale approvals dismiss when new commits land. Get those two right and most review-process arguments disappear - the repo states the policy, not the loudest voice in the thread.
The GitHub pull request review process, step by step
- Author opens or updates a pull request on GitHub.
- CodeCritic runs from the dashboard, a webhook on
pull_request events, or the GitHub Action in your workflow file. - Findings appear in CodeCritic and, where configured, as comments on the PR diff.
- Human reviewers triage AI output, discuss blocking items, and approve when risk is acceptable.
Two habits keep this process fast. Keep pull requests small enough that a reviewer can hold the whole diff in mind - a 400-line change gets shallow comments, a 40-line change gets real ones. And describe the change in the PR body: what problem, why this approach, what you already ruled out. Reviewers who have to guess intent write vague comments.
Prefer to start in the browser? Try online code review on snippets before you wire GitHub org-wide.
Code review without a pull request
Not every change flows through a PR, and GitHub still gives you review surfaces. The compare view (/compare/branch-a...branch-b) shows a diff between any two refs with line comments - useful for reviewing a long-running branch before it is PR-ready. For local or pre-PR work, git diff main...feature plus a paste into diff review gets structured findings on a patch without opening anything on GitHub. Full review features like approvals only exist on pull requests - compare view and local diffs cover the reading, the PR covers the merge decision.
Code review on GitHub vs linters and CI
CI and linters answer whether encoded checks pass - tests, formatters, policy rules. GitHub code review answers whether the change is acceptable to merge given intent, architecture, and risk. CodeCritic sits between them: after deterministic gates, before human sign-off. It complements your existing integrations, not replaces them.
When to use the GitHub Action for code review
Use the official Action when every pull request or push should get the same automated review in CI - especially when you want PR comments without someone clicking run in the dashboard. Start with dashboard or webhook runs for pilots; graduate to Actions once comment quality and false-positive triage look right for your team. For a staged org rollout and pre-merge gate habits, see the AI review rollout guide. Setup steps live in the user guide.