Faster & safer code merge. Automate your pull requests and leverage merge queues.
Joined March 2018
- Tweets 698
- Following 19
- Followers 499
- Likes 648
84 Photos and videos
Mergify retweeted
Jun 10
Your merge queue makes everyone wait.
In a monorepo, one queue forces unrelated PRs into a single line. One broken PR blocks the rest.
Scopes fix it: Mergify tags what each PR touches and runs independent scopes as parallel lanes.
We run this on our own monorepo every day 👇
1
1
252
May 21
If you don't know yet about Mergify Stacks, here's a quick demo from one of our engineers, Julian.
45
Mergify retweeted
May 8
10 coding agents in parallel -> 40 PRs -> all merged within an hour!
thanks to @mergifyio. it's a saviour!
6
1
5
181
Apr 27
A merge queue is critical infrastructure. Build it accordingly.
mergify.com/blog/merge-queue…
1
53
Apr 10
Your monorepo merge queue is a linked list. It should be a DAG. Here's why that matters: mergify.com/blog/monorepo-me…
53
Mergify retweeted
Apr 8
A shell script on Slack started a dashboard arms race at @mergifyio . Four days later, @JulianMaurin had a native macOS app on the App Store. Zero prior Swift experience.
mergify.com/blog/dashboard-a…
1
1
173
Feb 4
Introducing Merge Queue Academy
A free resource to learn everything about merge queues:
• How they prevent broken main branches
• Two-step CI, batching, speculative checks
• When you need one (quiz included)
merge-queue.academy
78
Feb 4
New on the blog: "Claude Didn't Kill Craftsmanship"
On why AI shifts engineering craft from code output to product thinking — and why that's actually more like craftsmanship than before.
mergify.com/blog/claude-didn…
51
Jan 22
New on the blog: How a LATERAL JOIN saved our API from production timeouts.
TL;DR: A naive subquery scanned 660K rows to return 50.
Switching to LATERAL JOIN: 1000x faster.
Full breakdown with EXPLAIN ANALYZE 👇
mergify.com/blog/on-lateral-…
2
79
10 Dec 2025
New case study! ⚡️
@cerebras, builders of the world’s fastest AI systems, use Mergify to keep a massive monorepo stable despite CI jobs running hours. Batching, two-step CI, and automation = predictable delivery under extreme load. Read how they do it: mergify.com/customers/cerebr…
1
1
181
27 Nov 2025
We just shipped Monorepo CI for GitHub Actions: detect which parts of the repo a PR touches, run only the jobs that matter, and expose a single CI gate for branch protection & merge queues.
Smarter CI, lower costs.
mergify.com/blog/monorepo-ci…
1
45
7 Nov 2025
Ever wondered where the ** in **/*.c actually comes from?
mergify.com/blog/origin-and-…
31
5 Nov 2025
How do you ship risky code without crossing your fingers?
We ran old and new logic side by side in production: no impact, just data.
This "shadow shipping" pattern turned feature-flag anxiety into real rollout confidence.
👉 mergify.com/blog/shadow-ship…
26
31 Oct 2025
Why does PostgreSQL ignore your index and scan the whole table anyway? 🤔
At Mergify we hit this on tables with 100M rows. Turns out it’s not a bug: it’s planning math.
See how we nudged the planner to do the “right” thing instead of fighting it:
👉 mergify.com/blog/why-postgre…
1
141
23 Oct 2025
We built a "self-healing" system that fixes deprecated configs by opening PRs automatically.
It worked like magic, until it didn’t.
Here’s the story of automation that got too smart for its own good:
👉 mergify.com/blog/the-magic-a…
24
22 Oct 2025
TypeScript doesn't actually run, but your bundler might think it does.
Our latest post explains why marking your type imports with 'import type' (and using 'verbatimModuleSyntax') makes your builds faster and cleaner.
Read more 👉 mergify.com/blog/typescript-…
37
15 Oct 2025
AI can read your code — but not your mind.
Our new post explores why documentation still matters in the age of AI, and how it’s becoming the bridge between human intent and machine understanding.
mergify.com/blog/should-we-s…
23
8 Oct 2025
WARNING is the junk drawer of logging — full of “just in case” noise that hides real errors.
We explain why it’s time to delete it (and what to do instead).
🧠New on the Mergify Engineering Blog 👇
mergify.com/blog/why-warning…
20