How it works

Nothing runs on your infrastructure and nothing is added to your repository. You open a pull request; EasyMerge reads the diff and comments on it.

From push to comments

1. You open a pull request, or push to one. No button, no workflow file. Drafts wait until you mark them ready for review.
2. The check run appears. EasyMerge Review shows on the head commit as queued, then in progress.
3. The review runs. Files you have excluded, and files GitHub gives no diff for, are left out. You can watch progress in the dashboard, where findings appear as they are produced.
4. The comments land. One GitHub review carries the recommendation, the written summary and the merge confidence; each finding is an inline comment on its own line. One review means one notification, not one per comment.
5. The check run closes as success, failure, or cancelled.

How long it takes

Time grows with the size of the diff. The review detail page shows how long each review took, and the dashboard shows the median across your completed reviews — that is the figure to judge your own repositories by. Excluding generated code and splitting large branches both shorten it; see Large pull requests.

A review that hits a temporary problem retries on its own, so it may sit in progress longer than usual before it completes or fails.

What you see while it runs

The dashboard shows the review's status — Queued, Preparing…, Reviewing…, then Completed, Failed or Cancelled. Statuses and what each one means for you are in Review lifecycle.

A pull request event EasyMerge is configured not to review gets no review at all. Instead the check run closes as neutral, titled Review skipped, naming the reason.

Fresh reviews and repeats

Every push starts a new review of the updated diff. Reviews are never resumed or amended, and comments from earlier reviews stay on the pull request.

A commit that has already been reviewed is not reviewed again. Reopening a pull request, or any other event that arrives without a new commit, leaves the existing review as it is. Push a commit to get a fresh one.

Closing or merging a pull request mid-review cancels it, so comments never arrive on a PR you have already merged.

Next

• Quickstart — install the GitHub App and trigger your first review.