Review your first pull request

What you will build

By the end of this tutorial, you will have:

• Opened a pull request in Control Center’s PR workbench
• Read its diff and left an inline comment
• Submitted a review verdict
• Merged the PR

Prerequisites: Dispatch your first agent completed and one open pull request on a repo registered in this workspace. For the review steps, pick a PR you did not open — the Review button is hidden on your own PRs. Merge still works on a PR you authored.

Step 1: Open the pull request

1. Click Pull requests in the sidebar
2. Find your PR and click it

Checkpoint. The PR opens as a tabbed workbench — Overview, Diff, Source control, Chat, Actions — focused on Overview: the title and actions, the description and activity timeline and a sidebar with status, reviewers, assignees, checks and changed files. Clicking a file there jumps to it in the Diff tab. The PR review tab is not open until someone asks for an AI review.

Empty queue with a “connect GitHub” prompt

That state means the server holds no GitHub token — your client never holds one. Set one under Settings → Workspace → Profile & identity → Code hosting, then refresh the list.

Step 2: Read the diff

Open the Diff tab. A collapsible file tree sits on the left and the strip above the diff carries a commit-range selector — narrow the diff to one commit or a span of them — plus the file count and the running additions and deletions.

The settings button in the diff toolbar controls how it renders:

• Split or unified view
• Wrap lines or scroll long lines
• Code font ligatures

Mark a file as viewed to track your progress through a large diff. Keyboard navigation is in Keyboard shortcuts.

Step 3: Leave an inline comment

1. Hover a line in the diff — a small + pill appears in the gutter
2. Click it to comment on that line, or drag it vertically first to select a range
3. Type your feedback. The composer offers two submits:
   • Start a review (or Add to review if a review is already in progress) queues the comment. The thread shows Pending review until you submit a verdict in step 4.
   • Add single comment posts it to GitHub right away. The thread shows Posting…, then Synced, and offers a retry if the post fails.

For this tutorial, use Start a review so the comment goes out with the verdict.

A queued comment is not on GitHub yet

Start a review / Add to review hold the comment locally until you submit a verdict. Only Add single comment posts immediately. The review body you write in step 4 is a separate draft.

Step 4: Submit a review

1. Click Review in the Overview action row — the same button also sits in the Diff tab’s toolbar. It is hidden on PRs you authored and on a closed or merged PR.
2. Write a summary in the composer. It autosaves as a draft, so you can close the overlay and come back.
3. Choose a verdict:
   • Request changes
   • Comment
   • Approve

The verdict is the button. After Approve or Request changes, the button relabels itself to Approved or Requested changes. A Comment verdict leaves it labelled Review.

Checkpoint. The button reads “Approved” or “Requested changes” if you picked one of those two.

Step 5: Merge

The Merge button is present whenever GitHub reports the PR mergeable — it is not gated on your own approval. Its colour reports readiness rather than permission: primary when required approvals and checks are green, secondary while a check is still running, destructive when a requested reviewer has not approved or a check is failing.

1. Click Merge
2. Pick a method: Squash and merge, Create a merge commit, or Rebase and merge
3. For the first two, edit the prefilled commit title and message
4. Confirm

Any outstanding problems — “Checks failing”, “Some reviews are pending” — are listed in the flyout before you confirm.

Merging is irreversible

Merging pushes commits to GitHub. It never enters Control Center’s undo stack and cannot be undone from here.

After merging, a PrMerged domain event fires; analytics and notifications consume it. See Domain events for what else listens.

Reviewing with AI

Control Center can put a reviewer pipeline on an open PR, but only when you ask: the pr_review template has a manual trigger and nothing else.

1. Open the overflow menu in the Overview action row and choose Ask AI. Control Center starts the run and opens the PR review tab, so you can watch the specialists work.
2. Reviewer agents record their findings as review nodes in the PR’s space; a final step consolidates them into one report.

The pipeline deliberately does not post to GitHub — it ends after consolidating. Publishing is a separate step you take yourself, with the Publish to GitHub button on the PR review tab. See Use AI-powered review.

Recap

You opened a PR in the workbench, read the diff with syntax highlighting, left an inline comment, submitted a verdict and merged — without leaving the app.

Next: Build your first pipeline to automate multi-step workflows.