Pull request reviews
Most incidents start with a change. Polylane reviews every pull request in a connected repository against the production resources it deploys to, and posts one comment that says pass or fail.
What it does
An agent reads the diff and the live metrics, logs and open issues of the resources the repository deploys to, then decides whether the change can hurt production. You get one comment on the pull request, an optional Polylane production impact check, and a thread in the console with the full analysis.
How it works
- Opening a pull request against the default branch, pushing to it, or marking it ready for review starts a review of its head commit. Drafts are not reviewed.
- A later push replaces the review in progress, so only the latest commit is judged.
- Changes that touch only documentation, tests or CI files pass without an investigation.
- Polylane follows the repository's deploy edges to its production resources, or reviews against the workspace's cloud accounts as a whole when it has none.
- The agent investigates in a thread and records a
passorfailverdict. - One comment per pull request is edited on each review. A fail reads Hold this merge with the impact level and the finding; a pass reads Production impact unlikely, or says whether a fix for a detected issue is expected to resolve it. When a later push addresses a concern, the comment flips back to a pass and says so.
The agent can also suggest observability improvements, as one batched review of suggestion comments or a stacked pull request. They never affect the verdict.
Acting on a review
Mention @polylane in a comment on the pull request and Polylane answers in the same conversation; non-members receive a note about access instead.
| You ask for | What happens |
|---|---|
| A question | The agent answers from the review thread, with the evidence in front of it. |
| Another look | The agent reviews the latest push again and reconsiders the verdict. |
| A fix | Polylane starts a fix run and opens a stacked pull request against the pull request's branch, linked from the comment. |
The repository's Changes tab in the console lists every review. A fail offers Fix with Polylane, which starts the same fix run, and Dismiss when the concern does not apply: the pull request keeps being reviewed but gets no more comments until you Restore it.
| Status | Description |
|---|---|
| In review | Polylane is reviewing the latest push. |
| Flagged | The review found a production concern. |
| Passed | No production concerns found. |
| Resolved | A later push addressed the concerns. |
| Dismissed | A member dismissed the review; the pull request gets no more comments. |
Configure
Reviews are on for every connected repository. Settings > Pull request reviews turns them off workspace-wide and sets whether review threads are shared with pull request viewers. Under Settings > Repositories, a repository's Settings tab adds three fields.
| Field | Description |
|---|---|
| Review pull requests for production impact | Turns reviews off for this repository only. |
| Pull request review instructions | Free text the agent reads on every review: deploy-critical paths, or concerns other gates already handle. |
| Block merging on production concerns | Posts the Polylane production impact check on every reviewed pull request; it fails on a concern. On by default. Require it in branch protection to block merging. |
The check also completes on merge queue commits, since the pull request was reviewed before it entered the queue. A fail verdict can send the Production Concern Found email, off by default under Notifications.
Plan notes
Each plan includes a monthly number of pull request reviews; the Free plan's allowance is listed on Billing and usage, and members are emailed as it runs low. Past the allowance, the console records the pull request as Production impact not verified and nothing is posted to GitHub.
Related
- Repositories to connect a repository and link its resources.
- Fix runs for how a review thread reaches its verdict.
- Autofix for the pull requests a fix run opens.
- Notifications for the email a failed review can send.