Skip to content

Troubleshooting ​

Start with the surface where the problem appears:

SymptomFirst place to check
No review on GitHubThe EasyMerge Review check and repository settings
Repository or organization missingDashboard organization switcher and Sync From GitHub
File missing from a reviewThe review detail's Skipped group
Review failed or was cancelledReview detail status and reason
Security alerts missingSecurity Center → Repositories
Configuration scan failedProject Status and its last successful snapshot
Scans, syncs or automations pausedThe suspension message on the page

Retry with evidence

Before opening a ticket, note the pull-request URL, displayed status, approximate time and what you already retried. This is usually enough to start an investigation without sharing code or secrets.

No review appears on a pull request ​

Work down this list:

  1. Is the app installed on that repository? GitHub → Settings → Applications → EasyMerge → Configure. A repository added to an organization after an "only select repositories" install is not covered until you add it.
  2. Are reviews enabled? Check the toggle on the repository's settings page.
  3. Is the pull request still a draft? Drafts are skipped by default. Mark it ready for review, or turn off Skip draft pull requests.
  4. Is the event one you trigger on? opened and synchronize are on by default; reopened is not. See Trigger on PR events.
  5. Did the PR event actually happen? Editing a title or description does not trigger a review. Push a commit.
  6. Is the check run there? If EasyMerge Review shows as queued or in progress, the review is running; large pull requests take longer. If it says Review skipped, its summary names the reason.
  7. Was the PR opened while reviews were off? Turning them back on does not review it retroactively. Push a commit.
  8. Has that commit already been reviewed? A commit is reviewed once. Reopening a pull request you have not pushed to produces nothing new; push a commit.
  9. Is Post review on GitHub off? Then nothing reaches the pull request by design, not even a check run. Open the repository in the dashboard; the review and its findings are there.
EasyMerge Review · check run on the head commit

Review skipped

○ Neutral

EasyMerge review is disabled for this repository.

The repository is missing from the dashboard ​

Press Sync From GitHub on the dashboard home.

Sync From GitHub button on the dashboard home
The button sits at the top right of the dashboard home.

If it still does not appear, the installation does not cover it; add it on GitHub, then sync again. A repository that was removed from the installation comes back with its earlier reviews and findings intact.

Check the organization switcher too: with a single organization selected you only see that account's repositories.

If the page says No GitHub App installation found, the app is not installed anywhere you can see; go through Install the GitHub App.

An organization is missing from the switcher ​

If you were given access after you signed in, reload the dashboard or press Sync From GitHub; both re-check your access with GitHub. You do not need to sign out.

If it still does not appear, GitHub does not report you as having access; confirm on GitHub that your account can see the installation.

A teammate cannot see anything ​

They must sign in to EasyMerge at least once with their own GitHub account; access comes from GitHub per user.

If they signed in before being given access, a reload is enough. If they still see nothing, confirm on GitHub that their account can access the installation's repositories. With no access, Reviews and Dashboard are empty rather than showing an error.

The settings page is read-only ​

Expected for everyone except the person who installed the app on that account. The View only badge means exactly that. Ask them to make the change.

Repository settings with a View only badge and a notice that settings are read-only
Members see the badge and a read-only notice.

A file was not reviewed ​

Open the review detail and select the file in the Skipped group. Its label and the pane on the right say what happened:

Review detail with the Skipped group open and an excluded file selected
An excluded file and the pattern that matched it.
LabelPane saysMeaning
excludedExcluded by pattern: <pattern>That pattern is in the repository's exclude list
too largeNo diff available; the file is binary or too large to review.GitHub provided no diff
skippedmax_files_exceededThe pull request had more reviewable files than Max files per review allows

The pane names the exact pattern. Every pattern is yours to remove, including the starting ones; delete it on the settings page and the file is reviewed from the next review.

For a file past the cap, exclude generated code and fixtures to free room, or split the pull request.

The review says Failed ​

Usually a temporary outage, not your code. No inline comments were posted; the pull request carries one Review could not be completed comment linking back to the dashboard.

Review detail of a failed review showing that 4 of 7 files were reviewed
A failed review keeps its partial findings in the dashboard; **Retry review** is in the header.

The detail page shows how far it got: Review failed if nothing was read, or Review didn't finish with partial findings, which are not posted to the pull request.

Push a commit to run a fresh review. If it keeps failing on one pull request, note the PR link when reporting it.

The review says Cancelled ​

Review detail showing the Cancelled status and its reason
The reason appears under the status bar.

The page names the reason. Most often you pushed another commit (A newer commit replaced this review.), and the review of the new commit is the one to watch. Otherwise the pull request was closed or merged mid-review, or its base branch moved; push a commit to review again.

Reopening starts a review only if reopened is ticked under Trigger on PR events; pushing a commit always does.

The review has a summary but no inline comments ​

Either no finding held up, or your settings held them all back. ◌ Findings kept in EasyMerge means the severity or comment-limit settings kept them off the pull request; open the review detail to see why each one stayed there.

easymerge[bot] commented on this pull request

EasyMerge review

◌ Recommendation: Findings kept in EasyMerge

None of the findings met the repository’s comment severity or limit settings, so nothing was posted inline.

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

If the missing findings are minor, info is the likely cause; it is off by default under Comment severities.

Fewer comments than the last review on the same code ​

Expected. Each push is reviewed from scratch against the pull request as it then stands, so a finding posted before may be dropped or scored differently.

Nothing happened when I reopened the pull request ​

A commit is reviewed once, so reopening after a completed review produces nothing new; push a commit. If the previous review failed or was cancelled, reopening starts a new one, provided reopened is ticked under Trigger on PR events.

Reviews are slower than expected ​

Time scales with the size of the diff. Excluding generated code and splitting large branches into smaller pull requests both help; see Large pull requests.

A project status scan failed ​

The page keeps the last successful result and identifies it as an older snapshot. A refused request from GitHub, a timeout or an unexpected failure is worth one more Scan configuration again before reporting. See When a scan fails.

No supported project files were found on this branch. is not a fault: the default branch holds none of the files the configuration scan reads.

Security Center has no alerts for a repository ​

Open the Repositories tab in Security Center. Setup required, Access required, a pending App-permission banner, stale data or a coverage gap does not mean the repository has no vulnerable dependencies.

If setup is healthy, use Sync metadata once. This refreshes data EasyMerge can read from GitHub; it does not start a Dependabot scan.

If a repository shows Status unavailable with Sign in again to refresh access, EasyMerge has not yet confirmed your access level on GitHub. Sign out and sign in again, then sync.

Scans, syncs and automations are paused ​

The organization's EasyMerge installation is suspended. Scan configuration, Sync metadata and Sync alerts are unavailable, and automations do not run and cannot be created, enabled or run by hand. Existing results, alerts and schedules stay readable, and schedules can still be paused.

The message on the page says who suspended the installation. If it was suspended on GitHub, an owner of the GitHub account can re-enable the app in GitHub's settings for installed apps. If EasyMerge suspended it, contact support.

The dashboard is missing the gauge and the heatmap ​

You are in Decision view, which groups repositories by project status instead. The picker under your username in the sidebar switches back to Technical view.

Decision view dashboard
Decision view has no gauge or heatmap.

See Technical and Decision view.

The dashboard stops updating live ​

It reconnects on its own and catches up on what it missed. If it does not, reload the page. With many tabs open you can hit the limit of eight live connections per user; close a few.

Reporting a problem ​

Open a support ticket from Help & Support, then New ticket. Report a problem on a review or repository page does the same and fills in that context for you.

Have these ready:

  • the pull request URL,
  • the review status shown in the dashboard,
  • what you expected instead,
  • roughly when it happened.

Attach screenshots or logs, but keep passwords and access tokens out of them. Replies arrive on the ticket, and the bell in the dashboard header tells you when one lands.