Enqueue
Add one Change or submitted stack to the target queue.
Land the change against the trunk it will actually meet.
The Vex Merge Queue turns accepted Changes into one ordered landing pipeline. It builds the candidate, requires and evaluates checks against the exact commit, records the outcome, and keeps the queue moving when an entry changes.
One queue / exact candidates
Queue order is part of correctness.
Every active entry is evaluated against a named target and a durable queue prefix. On Vex-primary targets, a follower can validate speculatively, but it only merges when that candidate is still the exact commit trunk would receive.
When an entry ahead changes, Vex-primary queues invalidate stale speculation and rebuild or reuse a candidate with matching provenance. GitHub-primary targets validate sequentially through GitHub.
Merge Queue · illustrative queue model
master · Vex primary
01Foundation stackExact target · checks passingMerged
02Navigation follow-upPredicted trunk · durable validationReady
03Next independent ChangeWaits on the validated prefixQueued
Vex-primary followers revalidate when the durable prefix changes
Build
Replay it onto the durable queue prefix and publish an exact candidate for validation.
Validate
Require and evaluate checks against the commit that would advance trunk.
Merge
Advance the configured authority, then reconcile every affected follower.
Controls for the real failure modes
Vex-primary or GitHub-primary
Each target has one merge authority. Vex can advance its protected source ref or execute through GitHub while keeping the queue vocabulary and audit trail consistent.
Stacks and GitHub pull requests
Native Vex stacks use the Vex-primary queue. Ordinary pull requests enter through a GitHub-primary target with the GitHub App installed and strict branch protection enabled.
Eject, repair, and retry
A failed or stale candidate records why it stopped. Fix the Change, then retry the same entry without pretending the failed validation never happened.
Pause and promote
Operators can pause the queue, cancel work, or deliberately promote an approved hotfix while the normal ordering remains visible to everyone.
GitHub-primary boundary
GitHub-primary targets validate one pull request at a time and cannot use GitHub's native merge queue on the same protected target. The GitHub App and strict branch protection are prerequisites; Vex remains the ordered audit and control surface.
Inspect the ordered pipeline
$ vex queue statusLand when the exact candidate passes
$ vex land '#677'Start with proof