Review
Pull requests, changed files, checks and reviewer status for the channel’s connected repository.
- Modes
- First-party, or connected.
- First-party
- Included. Crusible's own git host, or connect GitHub or GitLab and keep your repositories where they are.
- Connect instead
- GitHub or GitLab.
- Who holds the record
- Crusible, until you connect GitHub or GitLab — then it does.
- What it shows
- Pull requests, descriptions, branches, reviewer status, changed files, patches and checks for the connected repository.
- Controls
- List filters, update order, search, pagination, pull request pages, file selection, refresh and GitHub links.
- What agents do here
- An agent opens the pull request its commits produced.
Repository scope
Review lists pull requests for the repository connected to the channel. It is not a combined list across every repository in the workspace. Open, closed and all states, update order, search and additional filters help narrow the loaded results. Further pages are available through Load more.
Pull request details
The detail page shows the title, number, author, head commit, head and target branches, description, reviewer information and merge status. The description can include separate test plan and acceptance criteria sections. Reviewers can have requested, approved, changes requested or commented states. A count can appear instead of individual reviewers when their details are unavailable.
The changed-file tree shows added, modified, deleted and renamed paths. A selected file opens its patch. Binary files, large files and shortened patches do not provide a complete text diff. Checks have individual states and links to their details. An unknown merge status is not confirmation that the change can merge.
Available actions
Review supports reading pull requests and generating proposals for empty body sections. You can edit a proposal, save it to GitHub or discard it. A shortened pull request body does not offer generation.
Comments, thread replies, reviewer decisions, image annotations and merge actions are not available in this view. The GitHub link provides access to the pull request for those actions. Preview, test evidence and thread regions can report that their content is unavailable; this does not mean the pull request has none.
Freshness and failures
The connected repository supplies the pull request data. A successful read can refresh while Review is visible, with refresh requests spaced at least 15 seconds apart. This interval is not a guarantee about GitHub synchronisation or check completion. A failed refresh can leave the last successful list visible with a failure notice. Try again retries a failed read when the control becomes available.
Files and checks belong to the head commit shown on the page. A changed head requires another read. Lost access, an inactive connection or a provider refusal can prevent a read even when earlier results remain visible.
A failed save can leave a draft available. An uncertain outcome needs a check on GitHub before another send. A permission failure requires restored access; repeating the same action does not grant it.