Reviews
Reviews is the code-review inbox for Colony Cloud. Route: /dashboard/reviews
It surfaces every open pull request that Colony has raised and that is waiting for a human reviewer. From the list you can jump directly into an inline diff view, leave comments, and trigger review actions — all without leaving the dashboard.
List view
Section titled “List view”The list view shows all open reviews across your enabled repositories.
Filtering
Section titled “Filtering”Two independent filters narrow the list:
- Repository — the org-wide repo selector in the sidebar scopes the list to a single repository. Clearing the selector returns all repositories.
- Status — a dropdown in the page header filters by queue status:
| Status | Meaning |
|---|---|
| All statuses | No status filter applied (default) |
| Ready for review | PR is open and waiting for a human reviewer |
| Auto-merging | Colony is running the merge process — no reviewer action needed |
| Changes requested | A reviewer has requested changes; Colony is addressing them |
| Blocked | The review is stalled — usually a failing CI check or a merge conflict |
| In progress | A reviewer has started but not yet submitted a review |
The status filter is reflected in the URL (?queueStatus=...) and is therefore bookmarkable and shareable. The repository filter is driven by the org-wide repo selector in the sidebar and is not part of the URL.
Review rows
Section titled “Review rows”Each row in the list represents one pull request. It shows the repository, issue number, PR title, current queue status (as a badge), and how long the PR has been waiting for review. Click any row to open the per-PR detail view.
Empty state
Section titled “Empty state”When no reviews match the current filters, the page shows: “No reviews waiting for your attention.” with a link to the Pipeline surface (/dashboard/pipeline) to see what is currently processing.
Per-PR detail view
Section titled “Per-PR detail view”Route: /dashboard/reviews/:owner/:repo/:issueNumber
Click a review row to open the full detail view for that pull request. A breadcrumb at the top of the page links back to the Reviews list.
The detail view is composed of four panels:
| Panel | Location | What it shows |
|---|---|---|
| Review header | Top | PR title, repository, issue number, current status badge, and the branch name |
| Review actions | Below the header | Action buttons for the most common reviewer interventions (see below) |
| Context sidebar | Left column (desktop: 320 px fixed width) | Issue context card (issue title + truncatable description with a ‘View full issue’ link), Acceptance criteria checklist (each criterion marked verified/unverified, manual criteria badged), Pipeline checks list, Agent activity card (summary + optional transcript link), and Cost card (actual spend + optional predicted P10–P90 range) |
| Diff viewer | Right column | A horizontal file-tab strip at the top of the diff pane (each tab shows the file name with its +additions/−deletions and a status icon), and below it the inline diff with per-line comment threads |
Review actions
Section titled “Review actions”The action bar provides direct controls without requiring you to open GitHub:
| Action | What it does |
|---|---|
| Comment | Opens a modal to leave a review-level comment. The comment is posted to GitHub and immediately visible to the Colony agent. |
| Request changes | Opens a modal to describe the changes needed. Colony re-queues the issue for development with that feedback. |
| Approve & integrate | Opens a confirmation dialog. On confirm, integrates the change using your identity — the PR is merged in the VCS and this action cannot be undone. |
After any action completes, the detail view reloads automatically to reflect the updated state.
Inline diff and comments
Section titled “Inline diff and comments”The diff viewer renders a unified diff for every changed file. Click any line to open a comment input anchored to that line. Submitted comments are posted to GitHub and immediately reflected in the comment thread below the line. A horizontal file-tab strip above the diff lists every changed file; click a tab to smooth-scroll the diff to that file.
Relationship to Inbox
Section titled “Relationship to Inbox”Reviews and Inbox are distinct but complementary surfaces:
- Inbox (
/dashboard/inbox) is the broad operator-action surface for issues that need human attention, including blocked work, stalled execution, strategy proposals, and issues awaiting code review. Dead-letter records are separate operational records and do not have row-level Inbox controls. - Reviews is code-review-specific. It shows only pull requests and provides the inline diff tooling needed to complete a review. Issues that appear in Inbox under the “Needs you — awaiting human code review” section are the same PRs visible in Reviews.
Use Inbox when you want a triage-first view of everything requiring attention. Use Reviews when you are specifically working through open code reviews and want the full diff experience.
For the full tour of Pipeline, Insights, and Inbox, see Dashboards.