Skip to content

Reading a review ​

A completed review has a summary on the pull request and inline comments for its findings. The summary is one EasyMerge comment per pull request, updated in place as later runs finish, so it always describes the latest result rather than adding a second long summary.

The review body ​

The summary opens with an EasyMerge review heading and a status callout, followed by the counts and; when the review has findings; a row of severity badges.

GitHub preview ​

This is the same structure as it appears in a pull-request comment. The content of the summary and finding title changes with the review; the labels, badge order and layout do not.

easymerge[bot] commented on this pull request

EasyMerge review

⚑ Review status: Changes requested

The import path in db/client.ts may not resolve. Address the findings below before merging.

3 findings across 2 filesMedium confidenceConfidence: 6.0/10 · Medium
Critical: 1Warning: 1Info: 1High impact: 1

Severity and high-impact counts are coloured badges. Confidence uses a green three-bar indicator: three filled bars for High, two for Medium and one for Low.

The summary also carries a Finding status section showing which findings are still open at the latest commit. See Tracking findings across pushes.

The status reflects the review result:

Review statusWhen
⛔ Blockedat least one critical finding
⚑ Changes requestedat least one warning, no critical
◉ Commentsonly info findings
↻ Incompleteno findings, but some files were skipped
○ No new findings in this runno new findings, while EasyMerge is still checking whether findings from earlier runs are open at this commit
⚑ No new issues · 2 still openno new findings, but findings raised by earlier runs are still open at this commit
✓ No issues foundno findings, nothing skipped, and nothing from earlier runs still open

The callout contains a short summary written for the pull request. For the two "no new" statuses it points you to the Finding status section instead. It is guidance, not a GitHub approval or merge block: EasyMerge submits reviews as a comment, never as Approve or Request changes.

The counts include findings that stay in the dashboard because of your severity or comment-limit settings. A summary can therefore show ⛔ Blocked even where the critical finding is not posted on a diff line.

When findings were held back, a line under the badges says how many and links to the detail page:

2 findings are not posted inline (severity filter, comment limit, or already raised by another run); see them in EasyMerge.

If EasyMerge cannot calculate confidence, the whole confidence segment is omitted. A review with no findings gets 10.0/10 · High; it does not claim that the pull request is free of every possible issue.

The footer counts files and links back to the review in EasyMerge. When files were skipped, it names the count and reason, for example 3 skipped (excluded).

Merge confidence ​

Alongside the finding counts, the body carries a confidence reading out of 10; how safe the change looks to merge given what the review found.

ReadingScoreMeaning
High8.0 and abovesafe to merge
Mediumabove 5.0, below 8.0review before merging
Low5.0 and belowdo not merge

A review that finds nothing reads 10.0/10 · High. A review that could not produce a reading carries none at all, and counts as Unrated on the dashboard.

Confidence rates the pull request as the review saw it. It does not take your CI checks or test coverage into account, it is not a promise that the change is correct, and it is not a substitute for a human reviewer.

Inline comments ​

Each finding is attached to the relevant changed line or range.

easymerge[bot] commented on db/client.ts

WarningHigh impact · Unverified Prisma import path

The import path generated/prisma looks unusual. Prisma types normally come from @prisma/client or a path mapped in tsconfig.json.

Suggested change

import { PrismaClient } from '@prisma/client';

A High impact badge marks a finding that may affect more than the highlighted line. Suggestions can be committed from GitHub; review them first.

Review versions ​

Each push starts a new review of the pull request, so a review detail page can have several versions. It opens on the latest; once there are two or more, a v3 of 3 switcher appears in the header, and the reviews list shows a matching v3 chip.

Review runs menu listing v3, v2 and v1 with status, commit, finding count and duration
Each version shows its status, trigger, commit, findings and run time.
  • Pick an older version to see its own findings, summary and files. A banner marks it as not the latest, with a link back.
  • Retry review is available on the latest version only.
  • A change in the finding count (such as −2) appears only between versions that both completed.
  • Findings can carry a New, Reappeared or No longer detected badge, and you can show only the new ones or only the reappeared ones. See Tracking findings across pushes.

Severities ​

SeverityWhat it means
criticalBroken functionality, a security vulnerability, data loss or corruption, a crash, an injection or auth flaw
warningA likely bug or unhandled edge case, a race condition, missing error handling, a resource leak, a significant performance problem
infoMaintainability, a misleading name or comment, a minor improvement

Severity is judged per finding and then reconsidered with the whole pull request in view; a problem that looks critical while reading one file alone may be posted as a warning once the rest of the change explains it, and the other way round.