Auto-merge

Auto-merge is off by default. Until you turn it on, PatchWave analyzes and fixes pull requests, and you merge them.

Turn on auto-merge

1. Go to Settings → Auto-merge.
2. Set the Workspace default policy and click Save workspace default.
3. Turn on auto-merge for each repository, or apply the workspace default to all of them.

Policy options

A policy sets which updates can merge, by dependency type and version bump size.

Dependency type	What it covers
Development	Build, test, and tooling packages that do not ship with your product.
Production	Runtime packages used by your deployed application.
Transitive	Packages installed by your dependencies. Dependabot mostly updates these to fix vulnerabilities.

For each type, pick which bumps can merge: Patch, Minor, Major, or Non-semver.

The recommended policy merges every bump for development dependencies, and patch, minor, and non-semver bumps for production and transitive dependencies.

Each repository uses the workspace default unless you give it a custom policy.

What PatchWave checks before merging

A pull request merges only when:

• It’s up to date with your base branch and has no conflicts.
• It passes all required CI checks.
• Every update in it has a safe verdict and fits your policy.

PatchWave never auto-merges a fix it wrote. Those wait for your review.

If your default branch requires an approving review, let PatchWave bypass it.

Merge queue

PatchWave keeps a merge queue for each repository. It updates out-of-date pull requests from your base branch, re-checks them, and pauses the queue if checks fail on the base branch.

When you add pull requests to the merge queue from your inbox, PatchWave also approves each one on GitHub as you.

Patch says

Start with the recommended policy, then allow more bumps once you trust my verdicts.