Skip to main content
Anyone with access can comment on a PR. The ability to request changes or submit reviews that approve a PR is limited to admins.

Preview the changes

Check this before reviewing line by line. A mintlify[bot] comment normally appears on the PR within moments of the last push, with a status table and a View Preview link to the changed pages as rendered. It rebuilds on every new push, so it always reflects the PR’s current content. Mintlify preview deployment bot comment -screenshot
A PR with no bot comment is usually not a build failure - it is most likely a PR opened from a fork, which does not get an automatic preview. Ask the author, or see Manual (custom) previews for requesting one.

Open the PR for viewing

  1. Go to the repository and click Pull requests.
  2. Select a PR from the list.

Leave a general comment

  1. Select the Conversations tab.
  2. Scroll to the bottom of the page, write your feedback, and click Comment. GitHub PR comment field -screenshot

Comment on a specific line

  1. Select the Files changed tab.
  2. Locate the file and specific line you want to comment on.
  3. Put you mouse on the line and click the blue plus icon. GitHub PR line comment -screenshot
  4. Type your comment.
  5. Click Add single comment.

Annotations can lag behind the latest push

A check-run annotation on Files changed, such as one from an advisory check documented in Automated tests, reflects the commit it was generated against, not necessarily the PR’s current HEAD. GitHub attaches each annotation to the specific commit its check run was generated against, and the multi-commit diff view can still surface an old annotation next to a line a later commit already fixed. To see the true current state, check the Checks tab, or the latest run of the specific check, instead of trusting an annotation seen while scrolling a multi-commit diff. Watch for this especially on a PR that has had several pushes before you start reviewing.

Start and submit review

  1. Add one or more line comments as described above.
  2. Optionally, suggest a specific change that the author can accept and commit directly. Click icon and edit the text between the ```. GitHub PR suggest change write -screenshot GitHub PR suggest change preview -screenshot
  3. When you’re done, click Start a review. Alternatively, click Add review comment if you already started the review.
  4. Finished reviewing all the files.
  5. Click Review changes above the changes. GitHub PR Review changes button -screenshot
  6. Enter a description of your feedback and select the type. GitHub PR Submit review -screenshot
  7. Click Submit review.

What happens now?

  • Follow the discussion in the Conversation tab.
  • If you requested changes, follow up on those.
  • If you approved and all checks are green, you can merge the PR and delete the branch.