Review pull requests

Collaborate and work together on GitHub.

Step 3: Leave a review

You assigned yourself! :tada:

Pull request reviews ensure quality and maintain momentum of changes to your project.

When reviewing a pull request:

• Review the title and body of the pull request, and possibly any associated issue, to understand the intended change.
• Review the diff, the comparison of the proposed code, in the context of the whole project.
• For most things, try out the proposed change. Check if the actual change matches the intention. Find the repository's contributing guide to find out how to review the changes.

In your review comments:

• Identify potential issues, risks, and limitations.
• Suggest changes and improvements.
• Share awareness of upcoming changes that the pull request doesn't account for.
• Ask questions to verify shared understanding.
• Highlight what the author did well and should keep doing.
• Prioritize the most important feedback.
• Be concise and provide meaningful detail.
• Treat the pull request author with kindness and empathy.

When an approval or request for changes is not yet needed, consider using comments. An approval lets the author know you believe the pull request is safe to merge. Requesting changes lets the author know you believe the pull request is not ready to merge.

:keyboard: Activity: Leave a review

• On the pull request, click Files changed.
• Click Review changes.
• Add a comment with your initial thoughts on the pull request.
• Select comment. You won't be able to approve or request changes to your own pull request.
• Click Submit review.
• Wait about 20 seconds then refresh this page (the one you're following instructions from). GitHub Actions will automatically update to the next step.