FAQ

Do I need to add anything to my repository?

No. No workflow file, no config file, no dependency. Installing the GitHub App is the whole setup.

Can EasyMerge merge or approve my pull requests?

No. Reviews are submitted as comments, never as Approve or Request changes, and the app has no permission to merge or push.

Does the check run block merging?

Only if you add EasyMerge Review to your branch protection rules yourself. By default it is informational.

How do I re-run a review?

Push a commit. Every push to the branch starts a fresh review of the updated diff. There is no manual re-run button.

Why did I get no comments at all?

The review may genuinely have found nothing — the body would read ✓ Recommendation: No issues found. A review can also come back with a summary and no inline comments, when nothing held up against the whole pull request, or when every finding was held back by your severity and comment-limit settings — the body then reads ◌ Recommendation: Findings kept in EasyMerge and the findings are waiting in the review detail. If there is no review at all, check that reviews are enabled for the repository, that the pull request is not still a draft, that the event you expected is one you trigger on, and that the files you changed are not excluded.

Why is the review body different every time?

Because it is written, not templated. The body follows a fixed shape — a recommendation callout, the finding counts and confidence, a row of severity badges and a footer — but the prose inside the callout is written for your pull request. Occasionally it is absent, along with the confidence reading, and the shape stays. See The review body.

Can I turn off the summary in the review body?

Yes. Turn Post summary comment off on the repository's settings page and reviews post inline comments only. It applies from the next review. See Post summary comment.

Can I run reviews without anything appearing on my pull requests?

Yes. Turn Post review on GitHub off. Reviews still run in full and their findings are readable in the dashboard, but the pull request gets no inline comments, no summary and no check run. See Post review on GitHub.

Why is there a comment on a line the pull request deleted?

That is allowed. Findings are anchored to either side of the diff, so a comment can sit on a removed line when the problem is what the change took away.

Why is a file missing from the review?

It matched one of the repository's exclude patterns, GitHub provided no diff for it, or the pull request went past the file cap. Select it in the review detail's Skipped group and the pane names the exact pattern. Every pattern is editable, so if one is catching a file you want read, delete it.

Are draft pull requests reviewed?

Not by default. Skip draft pull requests is on, so opening a draft — and every push to it while it stays a draft — is skipped. Marking it Ready for review reviews the diff as it then stands. Turn the setting off to have drafts reviewed like any other pull request. See Repository settings.

I reopened a pull request and got no review.

Expected. reopened is one of the trigger events but it is off by default, so reopening on its own does not start a review. Tick it under Trigger on PR events, or push a commit — that triggers a review either way.

Why does a big pull request say some files were skipped?

Beyond exclusions, a review reads at most 50 files by default. Files past that cap are skipped; excluded and undiffable files are removed first and do not count against it. The cap is editable per repository — see Max files per review.

What is the Review skipped check run?

A pull request event EasyMerge chose not to review: reviews are off for the repository, the pull request is a draft, or the event is not one you trigger on. It closes as a neutral check with the reason in its summary, and no review is created — so the dashboard shows nothing for it. See Review lifecycle.

Can I turn off info-level comments?

They are already off. Comment severities on the settings page starts at warning and critical, so info-level findings are kept but not posted inline. Tick info to have them posted too. Findings held back this way are listed in the review detail as not posted · severity filter. See Comment severities.

Can I cap how many comments one review posts?

Yes, and it is capped by default: Max comments per review is on at 20. The most serious findings are posted first, so what gets cut is the least important; the rest stay readable in the dashboard as not posted · comment limit. Turn the toggle beside the number off to post every finding. See Max comments per review.

Can I configure EasyMerge per organization instead of per repository?

Almost entirely per repository. The one exception is the organization default Enable review for new repositories, which decides the value a repository starts with the first time it is synced. It does not override repositories that already exist, and everything that shapes a review — exclude patterns above all — stays per repository. See Organization settings.

Can I set how long EasyMerge keeps my review history?

Yes. EasyMerge automatically deletes review findings and project-status metadata after the period in your organization's Data retention (days) setting. Pull request diffs are processed entirely in memory and are never saved to our database. See Data and privacy.

What does the confidence rating on a review mean?

It is the review's own reading of how safe the change looks to merge, out of 10, based only on what it found: High (8.0 and above) means safe to merge, Medium (above 5.0) review before merging, Low (5.0 and below) do not merge. A review that found nothing reads 10.0/10 · High. It does not take your CI checks or coverage into account, it is not a verdict on whether the change is correct, and EasyMerge still never approves or requests changes. See Merge confidence.

Why is one of my reviews Unrated on the dashboard?

Either it produced no rating — the findings are still posted, but nothing rates them — or it completed before ratings existed; those are not scored retrospectively. Unrated reviews are listed beside the gauge and left out of the percentage, so they do not drag the High share down. Only completed reviews are rated at all. See Using the dashboard.

What is Builder mode?

A less technical view of the dashboard, picked under your username in the sidebar. In Builder mode the dashboard home shows project status instead of review activity, and a review detail becomes a merge recommendation with the findings grouped by what they affect, rather than a file-by-file list. It is a per-user choice — it changes nothing for your teammates, and nothing on your pull requests. New accounts start in Developer mode. See Developer and Builder mode.

Does EasyMerge read my repository outside pull requests?

Only if you ask it to. The project status scan reads a repository's file listing plus its README, dependency manifests and lockfiles, test and tooling configuration, CI workflows and deployment files — never your application source, and never anything that looks like a secret. It runs only when someone presses Scan project; nothing schedules it. Everything else EasyMerge reads is the diff of a pull request. See Data and privacy.

My project status says Needs update. What changed?

The status branch has moved on since the last scan, so the result you are looking at describes an older commit. Pushing does not rescan — press Scan again. See Project status.

Does project status affect my reviews?

No. It posts nothing to a pull request, creates no check run, and changes nothing about how a review runs. The only setting it owns is which branch it scans. See Status branch.

Why does the file count on a review not match the files in my pull request?

Skipped files are left out of both halves of it. 12 / 12 files reviewed means twelve files were eligible and all twelve were reviewed; anything excluded by a pattern, undiffable, or past the file cap is counted separately as 3 skipped. A review that is still running shows the eligible total on the right and climbs towards it.

Why does a comment sit on a line I did not change?

It should not. Findings whose line is not part of the diff are dropped before posting. If you see one, it is a bug worth reporting — include the PR link.

Does EasyMerge see my private repositories?

Only the ones you grant it, and only their pull request diffs. See Data and privacy.

My teammate cannot see our repositories.

They need to sign in themselves at least once — GitHub decides which installations each user can see. Installing the app does not automatically give every colleague dashboard access.

If they had already signed in before you gave them access, reloading the dashboard is enough: EasyMerge re-checks their access with GitHub on each visit, so signing out and back in is not needed.

Who can change settings?

Admins. The person who installed the app on an account is always one, and in an organization an admin can promote anyone else on the Members page. Everyone else has read-only access to the settings pages. See roles.

Does EasyMerge comment on formatting?

No. Pure style and formatting — indentation, quote style, line length — are deliberately left to your linter. Findings are about behaviour: bugs, security, edge cases, maintainability.

I pushed while a review was running and it went Cancelled.

Expected. A new commit abandons the review of the one before it, so you are not sent comments about code you have already replaced. The push starts a review of the new commit at the same time. See Cancellation.

Do the deep-review, security and style-only labels do anything?

Not yet. The settings page lists them under Label-based review profiles, and now also lets you tick which of them new pull requests should start with. Neither part is live: no label is put on a pull request when it opens, and adding one yourself changes nothing — every PR gets the same review. See Repository settings.

I reopened a pull request and still got nothing, even with reopened ticked.

A commit is reviewed once. If the last review of that commit completed, reopening produces nothing new — push a commit. If it failed or was cancelled, reopening does start a fresh review.

How do I contact support?

From the dashboard. Help & Support in the sidebar opens your tickets, and New ticket files one — or use Report a problem on a review detail page or a repository's settings page, which fills in the repository and the review for you. Replies come back on the ticket, and the bell in the header tells you when one arrives. See Help and support.

Who can see the support tickets I open?

Everyone linked to the installation you filed the ticket under, plus the EasyMerge support team — not only you. Anyone on that installation can also reply to the ticket and close it. Keep passwords, access tokens and other secrets out of both the message and its attachments.

My ticket is closed but the problem is back.

Open a new ticket. Once a ticket is closed it no longer accepts replies; only support can reopen it. See Closing a ticket.

Does it work on GitLab or Bitbucket?

No. GitHub only.

Which languages are supported?

EasyMerge reviews the diff as text, so no language is off-limits. Results are strongest in mainstream languages. Generated code, minified bundles and lockfiles are skipped by default, though you can remove those patterns.