Concepts
Reading a review
The summary, the verdict, inline findings, and review statuses.
The summary
When a review finishes, the Review in progress note on the pull request is replaced by an OpenMerge Summary. It contains:
- A short overview of what the pull request changes
- Up to four bullet points on the most important effects
- Whether the pull request is safe to merge, and why
- Files needing attention, when there are findings
- The verdict
Verdicts
| Verdict | Meaning |
|---|---|
| Changes requested | At least one blocking finding (High or Critical) must be resolved before merging. |
| Review complete | There are suggestions, but none of them block the merge. |
| Looks good to merge | No actionable issues were found in the changed files. |
A verdict is advice. OpenMerge never approves or blocks the pull request in GitHub, so your branch protection rules stay in control.
Inline findings
Each finding is posted on the line it refers to, in the new version of the file. A finding includes:
- A severity and a category
- What is wrong, why it matters here, and what could go wrong
- Replacement code, when a concrete fix is clear
Findings are also saved with the review. Open any review from the Reviews page to see them grouped by file and filter them by severity.
Review statuses
The dashboard shows one of these statuses for every review:
| Status | Meaning |
|---|---|
| Queued | The event was accepted and the review is waiting for a worker. |
| Reviewing | A worker is gathering context or the agents are reviewing. |
| Retrying | An attempt failed and OpenMerge is trying again automatically. |
| Completed | Findings and the summary were posted to the pull request. |
| Needs attention | Every attempt failed. The review detail page shows the last error. |
Something unclear or out of date? Open an issue.