Guard · Review queue

Review queue

The Review queue is one team-wide table of the code changes and pull requests waiting on a human reviewer. Each row shows the change, the diff-review findings rolled up for it, the assigned reviewer, and the status. It is a paid team capability on the hosted dashboard, and it is separate from the desktop Review tab, which reviews your local working-tree diff.

Start here if you want to review a diff line by line before it merges: Review queue (diff review). This page covers the hosted team queue those findings roll up into.

Where to find it

  • Hosted route: repoops.ai /team/review
  • List API: GET /api/team/review-queue (optional ?status=)
  • Mutate API: POST /api/team/review-queue { action: "assign" | "status", id, ... }
  • Data layer: website/lib/review-queue.ts

What it does for you

One place for everything waiting on reviewThe queue lists each change with its repo, PR number, and source in a single team-scoped table, most recently updated first. A team only ever reads its own queue; every query is scoped to the current team, and a member an owner has restricted to certain repos sees only those repos' items.
Assign a reviewer and move the item alongAn owner, admin, or member picks a reviewer from the team roster and sets status through open, in review, approved, changes requested, and merged; a read-only member sees the queue and cannot change it. Assigning a reviewer to an open item moves it to in review automatically. GitHub moves it too: an approved or changes-requested review sets that status, a dismissed review drops it back to in review, and a merge sets merged, which nothing moves it off.
See the review findings without leaving the rowWhen diff-review findings exist for an item, the row shows the total count and any high-severity count, with the top findings (severity, file, line, and rationale) on hover. The item's link opens the pull request for the full detail.
Distinct from the AI approval gateThis queue tracks human reviewer assignment and status on a diff or PR. It does not gate autonomous agent writes; that is the separate action-approval queue. Items arrive from the GitHub App: on a pull_request webhook, RepoOps resolves the team from the App installation that delivered it (the install-to-team map written when the App was installed, never the repo name) and upserts that change into the team's queue with its review findings. When the installation maps to no team, the review still posts on the pull request and no queue row is written.

Read more

Last updated