Pull requests

Open pull requests

Pull requests lists your projects' pull requests on GitHub and lets you review them without leaving OpenOrc. It reads everything through your own GitHub CLI, gh. Your review stays a draft in OpenOrc, and nothing reaches GitHub until you submit it.

Click Pull requests on the sidebar's rail.

Browse and filter

The project chip in the header picks one project, or All projects: every project whose remote is on github.com, each under its own heading.

Search pull requests… narrows the list by title, number, author or branch. Each row shows the number, the author, the branch it merges from and into, the lines added and removed, and when it last changed. Drafts are marked Draft, and GitHub's review state shows as Approved, Changes requested or Review required. Each project lists up to 50 pull requests per filter.

Read a pull request

Click a row to open it. The header shows its title, state, author, branches, line counts and number of files. Switch between Changes, the diff as GitHub shows it, and Description, the author's text. Open on GitHub opens it in your browser, and Refresh loads it again.

Draft a review

You can write comments yourself whichever reviewer is chosen:

1. On Changes, click a line number. Drag or shift-click across line numbers to comment on several lines.
2. Write the comment and choose Add comment.
3. Repeat for each finding.

The bar under the diff counts your draft comments. Click the count to list them, and use the buttons beside each one to edit or remove it. A comment belongs to the commit it was written on. When the author pushes new commits, the bar warns that the comments were written on an earlier version and will post there. To comment on the new commits, post or discard the draft first.

Let a model review

1. Set Reviewer to Model.
2. Pick a model, or an Orcling to review with its own model.
3. Choose Start review.

The model reviews in a thread of its own, named Review #<number>: <title>, in Plan mode. It works on a separate copy of the pull request on no branch, so your checkout isn't touched. It records each finding as a draft comment on the changed line and finishes with a summary. Its comments join your draft, labeled with the model's name. A link beside Reviewer opens the review thread. It says the model is reviewing while it works, and reads Review conversation once it is done.

After the author pushes again, choose Review again. The same thread continues on the new commits, checks whether its earlier findings were addressed and comments only on what is left or new. A draft with comments on the older commits has to be posted or discarded first. If you resolved the review thread, the next review starts a fresh one.

The model can't post, push or change files. You edit or remove its comments and decide what to submit.

Submit the review

1. Choose Submit review.
2. Write a Summary. A model's summary fills the field when you haven't written one; otherwise it appears below as Model's summary, with Add to summary.
3. Under Post as, pick You, or Reviewer app if you set one up.
4. Under Verdict, pick Comment, Approve or Request changes.
5. Choose Post review.

OpenOrc posts the summary, the verdict and every draft comment as one GitHub review, then clears what it posted from the draft. The bar then shows Review posted. and a View on GitHub link.

A review needs a summary or at least one comment, unless you approve. When you post as yourself, you can't approve or request changes on your own pull request. Discard draft deletes the draft's comments and summary instead.

What it needs

• The GitHub CLI, installed and signed in. Run gh auth login in a terminal. Without gh, the view says GitHub CLI not found.
• A project whose remote is on GitHub.
• To let a model review, an agent you are signed in to.
• To post as a bot, a reviewer app: in Settings, open Connections, find Reviewer app under GitHub and choose Set up. The app can approve only when Let it approve is on. See Settings.

Next steps