Pull request reviews

Review pull requests to provide feedback, suggest changes, and ensure code quality before merging.

在本文中

Pull request reviews let people comment on changes, suggest improvements, and approve or request changes before code is merged. Anyone with read access can review and comment on proposed changes, helping teams maintain code quality and share knowledge.

View pull requests awaiting your review

Review decision types

When a reviewer submits a review, they choose one of the following decisions:

DecisionMeaning
CommentLeaves general feedback without explicitly approving or requesting changes.
ApproveSignals that the changes are ready to merge.
Request changesFlags feedback that the author should address before merging.

Reviewers can also comment on specific lines, suggest exact changes, and discuss implementation details. Review conversations appear in the pull request timeline so the team can track feedback and decisions.

Requesting and requiring reviews

Reviews can be requested from specific people or teams when they need feedback from the right experts.

To request a review, you need write access to the repository. You can request a review from a person or team with read access to the repository, and they receive a notification.

  • Pull request authors can request reviews only if they are repository owners or collaborators with write access.
  • Organization members with write access or triage permissions can also assign a reviewer for a pull request.
  • If you request a review from a team and code review assignment is enabled, specific members will be requested and the team will be removed as a reviewer.

If you define code owners in a CODEOWNERS file, GitHub can automatically request review from owners when a pull request changes their code. See Requesting a pull request review.

Repository administrators can require approvals before pull requests are merged. Required reviews help protect important branches and reduce accidental merges. See 关于受保护分支.

Further reading