Appearance
Review lifecycle
Dashboard status vs GitHub result
The dashboard shows review progress. GitHub shows the corresponding EasyMerge Review check only when Post review on GitHub is enabled.
Statuses
The status of a review is shown as a badge in the dashboard, on the reviews list and on the review detail page.
| Badge | Meaning |
|---|---|
| Queued | Accepted, not started yet |
| Preparing… | Reading the pull request's files |
| Reviewing… | Files are being reviewed; findings appear as they arrive |
| Completed | The review finished, and was posted unless you turned posting off |
| Failed | The review stopped before it could be posted |
| Cancelled | The review was stopped before it finished |

A pull request whose files were all skipped still ends as Completed, headed Nothing to review; see When everything is excluded.
When a review fails
A failed review posts no inline comments. The pull request gets a single status comment instead, and whatever was read stays in the dashboard:
EasyMerge review
⚠️ Review could not be completed
EasyMerge encountered an unexpected error while reviewing this pull request. No findings were posted, so this result should not be treated as a clean review.
A later failed review on the same pull request edits that comment.
The review detail page shows how far it got:
- nothing read: Review failed, The review failed before any file could be analyzed. Nothing was posted to the pull request.;
- some files read: Review didn't finish, Reviewed 7 of 12 files before the run failed. The findings below are partial and were not posted to the pull request; retry to review the remaining files.
With spec review on, a code review that fails after reading the changes does not stop the spec review; it still shows its own result. A failure before reading the changes leaves the spec review without one.
Push a commit to run a fresh review.
The check run
EasyMerge maintains one check run named EasyMerge Review on the head commit:
| Review status | Check run | Title |
|---|---|---|
| Queued | queued | |
| Preparing…, Reviewing… | in progress | |
| Completed | success | Review completed |
| Failed | failure | Review failed |
| Cancelled | cancelled | Review cancelled |
Review failed
✕ Failure
The review stopped before it could be posted. Push a commit to run a fresh review.
An event EasyMerge did not review gets its own check run, completed as neutral and titled Review skipped. Its summary names the reason:
| Summary | Cause |
|---|---|
| EasyMerge review is disabled for this repository. | Enable AI review is off |
| This pull request is a draft; the repository is configured to skip draft PRs. | Skip draft pull requests is on |
| This repository is configured to not auto-review this pull request action. | The action is not ticked under Trigger on PR events |
Skipped by .easymerge.yaml (…): reviews.filters.… matched …. | A filter in the configuration file matched the pull request |
Review skipped
○ Neutral
This pull request is a draft; the repository is configured to skip draft PRs.
A skip creates no review, so nothing appears in the dashboard, and the next qualifying event is reviewed normally.
The check run never blocks a merge unless you add it to your branch protection rules.
With Post review on GitHub off there is no check run at all. The review still runs and its findings stay in the dashboard.
What triggers a review
A review starts when a pull request is opened or synchronized (a commit is pushed). reopened is off by default; tick it under Trigger on PR events.

Marking a draft Ready for review also starts one, whichever events you ticked; this picks up a pull request skipped while a draft.
If your repository has a configuration file, two more events can start one:
- a pull request skipped by a filter is reviewed once the reason goes away, such as removing an ignored label;
- changing the base branch to one with a different configuration file reviews it again with that branch's settings.
Nothing else triggers a review. There is no manual "review now" action, and editing the title or description does not start one, though the next review will read the edit.
The same commit is not reviewed twice
A review covers one commit. An event for a commit that already has a review creates nothing new; reopening without pushing is the usual case. Push a commit to get a fresh review.
The exception is a failed or cancelled review: an event for that commit starts a new attempt.
Cancellation
Three things cancel a running review. Each marks it Cancelled and names the reason on the review detail page and in the Review cancelled check run:
| Cause | Reason given |
|---|---|
| You pushed a new commit | A newer commit replaced this review. |
| You closed or merged the pull request | The pull request was closed before the review finished.; or merged, on the check run |
| The branch you are merging into moved while the diff was being read | The pull request's base changed while the diff was being read, so this review no longer matches it. Push a new commit or re-trigger to review again. |

Pushing is the common case: the older review is abandoned, so you never get comments on code you have replaced, and the same push starts the review of the new commit.
Reopening starts a fresh review only if reopened is ticked under Trigger on PR events. Pushing a commit after reopening always does.