Pull request impact assessments
Most issues start with a change. Praxen Inc. runs an impact assessment for each pull request in a connected repository. It checks the production resources that repository deploys to and posts a pass or fail comment. See repositories to connect a code host.
What it does
An agent checks the diff against live metrics, logs, and open issues for the affected resources. You get one comment on the pull request, an optional Praxen Inc. production impact check, and a thread in the console with the analysis.
How it works
- A pull request against the default branch gets an assessment when a member opens it or pushes to it. A draft gets an assessment when a member marks it ready.
- A later push replaces the assessment in progress, so only the latest commit gets a verdict.
- A change with no production effect can pass without a resource investigation.
- Praxen Inc. follows the repository's deploy edges to its production resources. If none exist, it checks the change against all cloud accounts in the workspace.
- The agent investigates in a thread and records a
passorfailverdict. - Praxen Inc. edits one comment after each assessment. A fail says Hold this merge and shows the impact level and finding. A pass says This change is unlikely to harm production. It can also say if a fix for a detected issue can resolve it. A later push that addresses a concern changes the comment to a pass.
The agent can also suggest observability improvements in one batch. Those suggestions do not affect the verdict.
Act on an assessment
Mention @praxen in a pull request comment. Praxen Inc. answers in the same conversation. Non-members get an access note.
| You ask for | What happens |
|---|---|
| A question | The agent answers from the assessment thread with its evidence. |
| Another assessment | The agent assesses the latest push again and reconsiders the verdict. |
| A fix | Praxen Inc. starts a fix run and opens a stacked pull request against the pull request's branch. |
The repository's Changes tab lists each assessment. A fail offers Fix with Praxen Inc., which starts the same fix run, and Dismiss when the concern does not apply. A dismissed assessment gets no new comments until a member selects Restore.
| Status | Description |
|---|---|
| Assessing | Praxen Inc. checks the latest push. |
| Concern found | The assessment found a production concern. |
| Passed | The assessment found no production concern. |
| Resolved | A later push addressed the concern. |
| Dismissed | A member dismissed the assessment. The pull request gets no new comments. |
Configure
Impact assessments run for every connected repository. Use Settings > Impact assessments to turn them off across the workspace. This page also controls whether pull request viewers can open assessment threads. Find repository fields under Settings > Repositories > Settings.
| Field | Description |
|---|---|
| Assess pull requests for production impact | Turns assessments off for this repository only. |
| Impact assessment instructions | A markdown file in workspace memory at preferences/repositories/<owner>/<repo>.md. The agent reads it for repository-specific guidance, such as deploy-critical paths and concerns that other checks cover. |
| Block merging on production concerns | Posts the Praxen Inc. production impact check for each assessed pull request. It fails when the assessment finds a concern. Require it in branch protection to block merging. On by default. |
The check also completes on merge queue commits. Praxen Inc. assessed the pull request before it entered the queue. A fail verdict can send the Production Concern Found email. This email is off by default under Notifications.
Plan notes
Each plan includes a monthly number of impact assessments. The Free plan's monthly limit appears on Billing and usage. Members get an email as the included impact assessments run low. After they run out, the console records Production impact not verified. Praxen Inc. posts no result to GitHub.
Related
- Repositories to connect a repository and link its resources.
- Fix runs for how an investigation reaches its verdict.
- Autofix for the pull requests a fix run opens.
- Notifications for the email an assessment can send.