Inside the Trenches of CI/CD
Stories, insights, and opinions from the team behind Mergify
Julien Danjou
November 27, 2025
∙
5 min
read
Run only the tests that matter in your monorepo. Mergify Monorepo CI detects which parts of your repo each pull request touches and triggers the right GitHub Actions jobs, then aggregates them into a single CI gate for branch protection or Merge Queue.
∙
5 min
read
Detecting Blocking Tasks in Asyncio by Measuring Event Loop Latency
CI/CD promises speed, automation, and confidence. But if you’ve ever stared at a red pipeline for hours, battled flaky tests, or deployed a “fully tested” build that still broke production—you know there’s a lot more to it.
Tomasz Biernacki
∙
5 min
read
Detecting Blocking Tasks in Asyncio by Measuring Event Loop Latency
CI/CD promises speed, automation, and confidence. But if you’ve ever stared at a red pipeline for hours, battled flaky tests, or deployed a “fully tested” build that still broke production—you know there’s a lot more to it.
Tomasz Biernacki
∙
5 min
read
GitHub Merge Queue Was Step One. Real CI Orchestration Comes Next.
CI/CD promises speed, automation, and confidence. But if you’ve ever stared at a red pipeline for hours, battled flaky tests, or deployed a “fully tested” build that still broke production—you know there’s a lot more to it.
Tomasz Biernacki
Join our community on Slack
Get tips, news, and resources from Mergify and its users.
Curious where your CI is slowing you down?
Try CI Insights — observability for CI teams.