Appearance
Repository settings
Repository settings control when reviews run and what reaches GitHub. Most review settings can also come from .easymerge.yaml.

Settings apply to one repository. Installation admins can change them; members can view them. Changes apply to the next review, not one already running.
An organization can choose whether new repositories start with reviews enabled, but it cannot override a repository after that. See Organization settings.
The page has two tabs:
- AI review holds the configuration-file status and everything about pull request reviews.
- Connection holds Project status (configuration scans and Dependabot alerts) and Spec review.
If the repository is private and your plan does not include private repositories, the AI review tab says so at the top: pull requests in that repository are not reviewed until the plan is upgraded.
Configuration file
Most review settings can also be set in a .easymerge.yaml file in the repository. The status bar at the top of the AI review tab shows whether the default branch has one and its state, such as Active · valid, No file or Unreadable, with a count of any issues. Open the count to see each issue and jump to its line in the file. While the file sets a value, that setting is marked From .easymerge.yaml and cannot be changed here; edit the file instead.
From the status bar you can Refresh the file's status, Validate YAML before committing a change, and Export as YAML to turn the current settings into a starting file. See Configuration file.
Two views sit under the status bar:
- Form shows the settings described below. Advanced review rules (language, verbosity, instructions, path rules and filters) come last, with a link to the line of the file that sets each one.
- .easymerge.yaml shows the file as stored on the default branch, with line numbers. Keys that override a setting on the page, and keys that exist only in the file, are marked in the margin. Beside the file, Applied from this file lists the keys in use and Not in this file — UI applies lists the settings that still come from the page. Keys that need Pro are marked ignored · requires Pro on other plans.
Review settings
| Setting | Default | What it controls |
|---|---|---|
| Enable AI review on Pull Requests | on | Whether EasyMerge creates reviews for the repository |
| Trigger on PR events | opened, synchronize | Which pull-request events begin a review |
| Skip draft pull requests | on | Whether drafts wait until they are ready for review |
| Max files per review | set for the repository | How many eligible files one review reads |
| Exclude Patterns | starter list | Files that are not reviewed |
| Post review on GitHub | on | Whether results are posted to the pull request |
| Comment severities | warning, critical | Which findings appear inline |
| Post duplicate findings to GitHub | off | Whether a finding already commented on an earlier commit is posted again |
| Post summary comment | on | Whether the review summary is posted |
| Max comments per review | on, 20 | The maximum inline comments per review |
| Default review profiles | none | Profiles added to each newly opened pull request |
Enable AI review

Turn this off to stop future reviews for the repository. Turn it back on before the next relevant pull-request event to review again.
Trigger on PR events

Choose opened, synchronize, and reopened. opened and synchronize are on by default; reopened is off. Marking a draft ready for review starts a review even when those events are not selected.
Skip draft pull requests
With this on, EasyMerge ignores draft pull requests until they are marked ready for review. Turn it off to review drafts like other pull requests.
Max files per review
The cap applies after excluded and undiffable files are removed. Files past the cap are skipped. Raising it can make wide pull requests slower; lowering it leaves more files unread. See Large pull requests.
Exclude Patterns

Exclude patterns are editable globs. A new repository starts with common generated files, lockfiles, and build output excluded; remove any pattern to review those files again. With an empty list, built-in exclusions such as .easymerge.yaml still apply.
See Exclude pattern syntax and Excluding files.
Post review on GitHub

Turn this off to keep reviews and findings in EasyMerge only. EasyMerge does not post inline comments, a summary, or a check run to GitHub while it is off.
Comment severities

Only selected severities are posted inline. warning and critical are selected by default; info findings remain available in the dashboard.
Post duplicate findings to GitHub
With this off, a finding that was already commented on an earlier commit of the pull request is not posted again; it stays visible in EasyMerge. Turn it on to post every finding on every push. It is available only while GitHub posting is on. See Tracking findings across pushes.
Post summary comment

Turn this off to post inline findings without a review summary. It is available only while GitHub posting is on.
Max comments per review

With the limit on, EasyMerge posts the most serious findings first and keeps any remaining findings in the dashboard. Turn the limit off to post every finding at the selected severities.
Spec review

Spec review is available on Pro. Choose a repository, branch, and optional path containing specifications; EasyMerge compares relevant code changes with those files. Leave the source unset to turn it off.
Only Markdown, text, YAML, and JSON specification files are read. A private specification repository can be used only where its sharing permissions allow it. You can re-run just the spec review after changing a specification.
Default review profiles

Choose the profiles that new pull requests should receive:
| Label | Profile |
|---|---|
deep-review | A thorough review across the whole diff |
security | Extra focus on security issues and vulnerabilities |
style-only | Formatting and style rather than deeper logic |
EasyMerge adds each selected label when a pull request opens and runs one review for each selected profile. With no profiles selected, it runs a Standard review. Changing this setting affects new pull requests only.
Project status
The Connection tab shows two checks of the repository: a configuration scan of its files and its Dependabot alerts from GitHub. Project status is separate from pull request reviews. Configuration scans always read the GitHub default branch; run one from Project status or schedule scans with a Pro automation. See Project status and Security Center.