Skip to content

Limits and defaults ​

Per-repository defaults ​

The values a repository starts with. All are editable by an admin on the repository's settings page, and most can also be set in a configuration file; see Repository settings.

SettingDefault
Enable AI reviewon
Trigger on PR eventsopened, synchronize (reopened off)
Skip draft pull requestson
Exclude patternsthe starting list
Post review on GitHubon
Comment severitieswarning, critical (info off)
Post duplicate findings to GitHuboff
Post summary commenton
Max comments per reviewon, 20
Spec reviewoff; available on Pro
Default review profilesnone

Marking a draft pull request ready for review always triggers a review, regardless of the trigger events chosen.

Because info is off by default, minor maintainability findings are kept but not posted inline. Findings held back; by severity, by the comment limit, or because another run already raised them; are counted in the review body and listed in the review detail.

Per-user defaults ​

SettingDefault
Display modechoose Technical or Decision view during first sign-in

Your display mode is yours alone; changing it affects no one else and nothing on your pull requests.

Organization defaults ​

SettingDefault
Enable review for new repositorieson
Data retention (days)Depends on your subscription plan; review findings and project-status metadata are deleted after the configured period

Merge confidence bands ​

ReadingScoreMeaning
High8.0 and abovesafe to merge
Mediumabove 5.0, below 8.0review before merging
Low5.0 and belowdo not merge

Only completed reviews are rated. One that produced no rating counts as Unrated and is left out of the percentage. See Merge confidence.

The starting exclude list ​

A repository's exclude list begins with these patterns. Every one of them is editable; remove any entry and the files it matched are reviewed again, and an empty list reviews every file.

text
*.lock
*.min.js
*.min.css
*.generated.*
**/*.d.ts
**/dist/**
**/node_modules/**
package-lock.json
npm-shrinkwrap.json
pnpm-lock.yaml
bun.lockb
go.sum
packages.lock.json
gradle.lockfile
.pnp.cjs
.pnp.loader.mjs
**/.yarn/**
**/build/**
**/out/**
**/.next/**
**/.nuxt/**
**/coverage/**
**/.turbo/**
**/__pycache__/**
**/.venv/**
*.map
*.bundle.js
*.pb.go
*_pb2.py
*_pb2_grpc.py
*.g.dart
*.freezed.dart
zz_generated.*
*_generated.go
**/__snapshots__/**
CHANGELOG.md
*.svg
*.csv
*.sqlite
*.sqlite3
*.sqlite-journal
*.sqlite-wal
*.sqlite-shm

The list covers common lock and dependency metadata, build and coverage output, source maps and bundles, generated code, test snapshots, and selected non-code assets. Lockfiles ending in .lock; yarn.lock, Cargo.lock, Gemfile.lock, composer.lock; are already matched by *.lock. See Excluding files.

Re-runs ​

ActionWhoLimit
Retry review on a failed reviewany memberthe latest run of an open pull request, when your plan and quota allow a review
Re-run the spec review of a completed reviewany membertwice per review; does not use review quota
Re-run N failed this month on the dashboardadminsevery eligible pull request in one organization whose latest review failed this calendar month (UTC)

Automations ​

Automations are available on Pro and always run on the repository's GitHub default branch.

LimitValue
Repository scopeone repository per automation
Frequencydaily or weekly
Run windowone hour, in UTC
Start-time precisionwhole hours only
Run deadline24 hours, then the run is Timed out
Missed windowskipped, not run later

Moving off Pro pauses every active schedule and cancels scheduled runs that have not started. Returning to Pro keeps the schedules paused until an organization admin enables them again.

Configuration file limits ​

Limits for .easymerge.yaml. A value past its limit is reported in the configuration-file status bar on Repository settings and ignored; a file past the size or nesting limit is ignored as a whole.

LimitValue
File size64 KB
Nesting depth10 levels
YAML aliases50
reviews.exclude patterns200
Length of a glob256 characters
Wildcard runs per glob (** counts as one)3
{…} groups per glob3
comments.max_per_review1 to 100
reviews.instructions4,000 characters
reviews.path_instructions25 entries, 1,000 characters each
All instructions together12,000 characters
reviews.path_rules50 rules
Each reviews.filters list50 entries
A title keyword64 characters
An author pattern64 characters
Problems listed per file50

The advanced keys (language, reviews.verbosity, instructions, path rules and filters) apply only on a plan with advanced review configuration (Pro).