Skip to content
UFO
Try UFO

Reviewing pull requests

Connect GitHub and give the pull request URL.

Review this pull request for correctness, regressions, security problems, and missing tests. Run focused checks where useful. Publish findings on GitHub. Do not change the branch or merge it.

Set the review scope

Section titled “Set the review scope”

Name risks such as permissions, billing, concurrency, migrations, or user-facing behavior. Provide the related issue or specification when the code changes do not explain all the requirements.

State where the review must go:

  • Conversation only keeps findings in UFO.
  • Publish on GitHub creates the requested GitHub review.
  • Fix findings allows branch changes after the review.

Your UFO does not publish or change the branch unless the request allows it.

Read the result

Section titled “Read the result”

Each reported problem includes the affected file, what can go wrong, and how to reproduce it. Questions and style preferences do not count as defects.

If UFO finds no confirmed problems, it tells you what it checked. It does not post an empty review comment.

See the complete pull request review recipe.