Mergify retweeted
mergify works like magic, when u have multiple prs that u want to merge at the same time, it will first merge those that do not have conflicts, then queue the one that requires conflict resolution last. @mergifyio
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
113
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 👇
If you don't know yet about Mergify Stacks, here's a quick demo from one of our engineers, Julian.
126
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…
1
95
Your monorepo merge queue is a linked list. It should be a DAG. Here's why that matters: mergify.com/blog/monorepo-me…
73
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
101
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…
63
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
99
Your Python app did not change.
A dependency did.
mergify.com/blog/stop-lying-…
65
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…
48
Goodbye Checklists, Hello AI Linters
mergify.com/blog/goodbye-che…
28
Ever wondered where the ** in **/*.c actually comes from?
mergify.com/blog/origin-and-…
34
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…
30
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…
25




