From the people who fix this for a living.
Long-form guides on the things that actually slow your team down. Written by Mergify engineers, drawn from thousands of CI pipelines and merge queues we have watched run in anger.
Topics
Merge Queue
Why your main branch keeps breaking, and what a modern merge queue actually does to keep it green.
Read the guide → GuideContinuous Integration
Every change, built and tested on every push. The mechanics are well known. What separates teams that get value from CI from teams that just pay for it is what they do with the signal.
Read the guide → GuideCI/CD Pipeline
Build, lint, test, package, deploy. The order is not arbitrary. Each stage filters the work so the slow, expensive ones only run on changes that already cleared the fast checks.
Read the guide → GuideTrunk-Based Development
One branch, short-lived feature work, a main that is always shippable. The model is simple. The plumbing that makes it work in a real org is what teams skip and regret.
Read the guide → GuideFlaky tests
Flaky tests are not random noise. They follow patterns, and the patterns are framework-specific. Named, fixed, quarantined.
Read the guide → GuidePlaywright
Microsoft's end-to-end testing framework. Real browser, auto-waiting actionability, multi-language support. The default for new browser-test suites and what makes a Playwright flake different from a Cypress flake.
Read the guide → Guidepytest
Python's de facto testing framework. Plain functions, plain asserts, fixtures that compose, a plugin ecosystem that covers everything from async to coverage. How to keep a pytest suite fast and trustworthy past a few thousand tests.
Read the guide → GuideQueue Analytics
What to measure on a merge queue: throughput, wait time, batch success rate, failure rate, stage breakdown. The numbers that turn a queue from a black box into a tunable system.
Read the guide → GuideTest Quarantine
Stop flaky tests from blocking merges without skipping or deleting them. What to quarantine, how long to leave it there, and the anti-patterns that turn quarantine into a graveyard.
Read the guide → GuideCI Auto-Retry
Auto-retry absorbs transient CI noise so engineers do not chase it. The trade is that blanket retry hides real flake patterns. How to retry conditionally and track what auto-retry is hiding.
Read the guide → GuideMonorepo CI
Running the full suite on every change is wasteful past a few dozen projects. Affected-projects detection plus a scope-aware merge queue is how monorepo CI scales without burning the bill.
Read the guide →More guides coming. Want one on a specific topic? Tell us and we will probably write it.