GitHub Docs: Reviewing proposed changes in a pull request
Documents reviewing pull request diffs file by file, line comments, suggested changes, pending review comments, mark viewed, submit review, approve, comment, request changes, stale review behavior, and required review caveats.
What this source can teach
Use this source to inspect a concrete implementation and the decisions visible in its context.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Change review | Choose change review when users are inspecting proposed edits, diffs, suggestions, tracked changes, or review comments before accepting, rejecting, applying, or requesting changes. | Selecting a change reveals the base content, proposed content, author, context, and exact scope affected by a decision. | GitHub documents reviewing proposed pull request changes, suggestions, pending review comments, viewed files, review submission, approve, comment, request changes, and stale review behavior. |
| Dangerous-action review | Choose dangerous-action review when the user is about to execute a high-impact action and needs to inspect the exact payload, risk, evidence, and side effects before it leaves the safe preview state. | The review is bound to a specific action ID, payload version, target, actor, permission scope, source context, evidence set, and policy trigger. | Supports reviewing concrete proposed changes, commenting, approving, requesting changes, and detecting stale review state before important action. |
Comparisons supported by this source
- Change review vs review before submit vs approval workflow vs review queue
GitHub documents file-by-file pull request review, suggested changes, pending review comments, mark viewed, approve, comment, request changes, and stale review behavior.
- Dangerous-action review vs destructive action confirmation vs typed confirmation vs human approval gate vs review before submit vs security warning
Supports inspecting concrete proposed changes, comments, approvals, request-changes outcomes, and stale review state.
Evidence Role
This source is treated as product-example evidence. Its value comes from the specific claims and setting described above.
Publisher: GitHub Docs. Last checked: .