Aviator
Merge queue and release automation that keeps main green — built for monorepos and high-velocity teams.
About
Aviator automates the tedious parts of shipping code: its MergeQueue validates pull requests before they touch main, so broken builds never land; ChangeSets coordinate groups of related PRs across repos as a single unit; TestDeck detects and quarantines flaky tests; and a stacked-PRs CLI keeps dependent PRs in sync. It is explicitly built for monorepos at scale, with parallel queues that test non-overlapping changes simultaneously and custom CI validations per queue. The pitch is simple: developers enqueue PRs and forget them instead of babysitting merges.
The honest picture: this is infrastructure for teams with real merge pain — a five-person team on a small repo will not feel the benefit. Merge queues add a layer of process and CI cost (an extra validation pass per PR), and adopting one means retraining muscle memory around how code lands. Pricing is sales-led, so small teams should check the free tier limits before committing.
What it can do
- MergeQueue: validated merges that keep main green
- Parallel queues for non-overlapping changes
- ChangeSets: coordinate multi-PR, multi-repo releases
- TestDeck: automatic flaky test detection and quarantine
- Stacked PRs CLI for dependent change chains
Setup
Install the Aviator GitHub app on your repos and configure merge rules (labels, required checks, queue modes) via the dashboard or config file. Developers enqueue PRs with a label or slash command.
Prerequisites
GitHub repositories with CI checks configured. Best value on monorepos or repos with 20+ PRs a day.
Use cases
Works with
Trust score — 7/10
Scored 7/10 (metrics tier, metrics-v1). Evidence: Verified via vendor site/docs/GitHub and reputable coverage, wave 52; Trending score 72/100 from researcher assessment.
Sources
Every fact above was checked against these sources. Where a claim comes from the provider and couldn't be independently verified, the text says so.