Skip to content

Your first review ​

When an eligible pull request starts a review, EasyMerge keeps the full record in the dashboard. With GitHub posting enabled, it also posts the result to the pull request.

What you will see

The dashboard tracks progress and keeps the review history. With GitHub posting enabled, a check run, summary comment and inline findings show the result on the pull request.

For review triggers, drafts and retries, see Review lifecycle.

On the pull request ​

Three things appear, in this order:

  1. The check run. EasyMerge Review shows up in the PR's checks list as queued, then in progress.

  2. The summary. EasyMerge keeps one summary comment on the pull request and updates it for each completed run. It opens with a review status; from ⛔ Blocked down to ✓ No issues found; then a short written summary, finding counts with a merge confidence reading, and a footer counting the files reviewed and skipped.

    The status is wording in the body, nothing more. EasyMerge always submits its review as a comment, so Blocked blocks nothing and Changes requested is not a GitHub changes-requested review.

  3. The inline comments. Each finding is attached to the line; or line range; it refers to, most severe first.

The run's GitHub review links back to the summary, while the inline comments stay attached to their lines.

Following it in the dashboard ​

Open Reviews to watch progress live; the status updates as the review progresses, without a page refresh. The list has one row per pull request, showing the state of its latest review; you can filter it by repository, by review status, and by PR author.

Opening a review shows every finding grouped by file, with line references such as lines 44–45 for multi-line comments, a summary bar (12 / 12 files reviewed, the comment count, how long it took, and the merge confidence), and a link straight to the pull request on GitHub.

EasyMerge review detail showing merge confidence, files and inline findings
Review Detail keeps the summary, affected files, diff and suggested fixes in one view.

For comment severities, suggestions and how to evaluate a finding, see Reading a review. If a review does not start or complete, use Troubleshooting.