Faster & safer code merge. Automate your pull requests and leverage merge queues.
Worldwide.
Joined March 2018
- Tweets703
- Following19
- Followers500
- Likes652
Mergify retweeted
Three things that have changed my life recently: litellm, mergify, daytona vm.
Game change-ing each in terms of adding real depth and capability.
@Lite_LLM @daytonaio @mergifyio
You can now install Mergify skills directly from Claude Code Marketplace:
/plugin install mergify@claude-plugins-official
Mergify retweeted
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 👇
Mergify retweeted
10 coding agents in parallel -> 40 PRs -> all merged within an hour!
thanks to @mergifyio. it's a saviour!
A merge queue is critical infrastructure. Build it accordingly.
mergify.com/blog/merge-queue…
Your monorepo merge queue is a linked list. It should be a DAG. Here's why that matters: mergify.com/blog/monorepo-me…
Mergify retweeted
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…
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
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…
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-…
Your Python app did not change.
A dependency did.
mergify.com/blog/stop-lying-…
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…
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…
Goodbye Checklists, Hello AI Linters
mergify.com/blog/goodbye-che…
Ever wondered where the ** in **/*.c actually comes from?
mergify.com/blog/origin-and-…
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…
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…
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…
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-…