Review open pull requests in GitHub
This article explains how to contribute to Microsoft Learn by reviewing pull requests (PRs) and adding your comments. You can read new topics and see proposed updates before they're published by checking a public GitHub repository's open PR queue. Community feedback on proposed updates helps the entire community.
With PR comments and reviews, you can:
- Add and reply to comments on the PR.
- React to comments with emojis like 👍, ❤️, and 🎉.
Prerequisites
- Create a GitHub account, if you don't have one.
Find a PR
In your browser, navigate to the repository in GitHub that you want to review. If you're not sure which repo to look at, find one that interests you in our list of Microsoft Learn repos.
If you're browsing documentation and don't know which repo it belongs to, select the Edit pencil icon at the top of the page. This action takes you to the source file on GitHub. The repository name is displayed in the upper-left corner of the page. For example, the following image shows the repo name location for the
azure-dev-docs
repo.Choose the Pull requests tab to see the open PRs for that repo. If the repo has a lot of PRs, use the Filters bar to filter by label, author, and more. Or use the Search bar to look for specific queries.
Open a PR by selecting the title link.
Review a PR
In the PR you're reviewing, select the Files changed tab.
Compare the original document to the edited one. The original document will be in red, and the proposed document will be in green. Any added text will be highlighted in the green (new) section, and any deleted text will be highlighted in the red (original) section.
Add comments or suggest changes by selecting the plus (+) icon to the left of the line you'd like to comment on. To select multiple lines, select and drag the plus sign.
You can only add comments or suggestions to lines that have been edited in the current PR. To make other changes, edit that file in your own PR.
A box will open. Enter your comments or questions there. If you'd like, you can use the buttons in the toolbar to format your text, add bulleted and numbered lists, or insert code blocks and images.
You can also suggest a change to the text in that line.
In the toolbar for the comment, select the +- icon (probably the icon furthest to the left). This is the Insert a suggestion button.
The text from the line you selected will be included in a code block (inside two sets of ``` backticks).
To suggest changes to text that includes a triple-ticked code fence (```), replace the outer/enclosing
suggestion
backticks with tildes (~~~
).Edit the text. Use the buttons in the comment box for simple formatting like bold, italics, and bullets, or use the Markdown syntax elements directly. You can also add comments to this box below the code-block section.
After you've made your comment, select Start a review. The PR author will be notified of your changes. If you used the Insert a suggestion button in the previous step, the author will be able to commit your suggestion directly to the document.
If you want to bring someone else into the conversation, you can @mention other contributors by their GitHub alias in your comments. Mentioned GitHub users will receive an email containing your comment. You can also use Markdown in your comments, and your comment's Markdown is rendered once you submit the comment.
In the Conversations tab, read through the comments. If you have questions or comments, add them to the conversation. You can also add reactions to comments by selecting the smiley face icon in the bottom-left corner of each comment.
Submit a review
Once you've added all your comments to the review, submit your review.
- Select the Review changes button in the upper-right of the Files changed tab to open the review submittal dialog.
- Enter a descriptive Review summary.
- Select the radio button for your desired review type, and then choose Submit review.
The PR author will receive notification of the review.
Next steps
To learn more about commenting and reviews, check out these articles in GitHub's documentation.