“At @SageOx we moved the most expensive checks even past the merge queue, to post main merges. So fast checks in PR (< 2 min), merge queue slightly longer tests, and main the longest/deepest tests (including BDD user intent). This drives latest code to our test servers fast. Cuts of release to prod only can include commit hashes that have passed the deeper extensive tests.”
Quote · x.com
From “Deepest tests after main, release only passed hashes”, found 2026-10-24.
A concrete variant that decouples landing from trusting: main moves fast, release eligibility is the gate. It trades a possibly-broken main for throughput, the opposite of the merge-queue guarantee that main stays green. Practitioner claim, no numbers given.
- Integrate
- Verify
AI-drafted