| title | About pull request reviews | ||||||
|---|---|---|---|---|---|---|---|
| intro | Collaborate on pull requests to improve code quality. | ||||||
| redirect_from |
|
||||||
| versions |
|
||||||
| shortTitle | About PR reviews | ||||||
| category |
|
Pull request reviews are one of the primary ways people collaborate on {% data variables.product.github %}. Reviewers can comment on changes, suggest improvements, and approve or request changes before code is merged. This collaborative process enables teams to ensure code quality and share knowledge.
{% raw %}View pull requests awaiting your review{% endraw %}
Anyone with read access can review and comment on proposed changes. When submitting a review, choose one of three statuses:
- Comment: Share feedback without approving or requesting changes.
- Approve: Approve the changes for merging.
- Request changes: Identify issues that must be fixed before merging.
You can comment on specific lines, suggest changes for authors to apply directly, and discuss implementation approaches. Reviews appear in the conversation timeline and merge box. Mark conversation threads as resolved to track addressed feedback.
Repository owners and collaborators can request reviews from specific people or teams. When you define code owners in a CODEOWNERS file, they're automatically requested as reviewers when a pull request modifies their code. You can re-request reviews after making significant changes.
Repository administrators can require approvals before pull requests are merged, ensuring code quality and preventing accidental merges. For more information, see AUTOTITLE.
- AUTOTITLE
- AUTOTITLE
- Learn more in the Review pull requests {% data variables.product.prodname_learning %} course