We Built a Merge Queue Mode That Skips the Safety Check on Purpose

Mergify's merge queue now offers three distinct modes—serial, parallel, and isolated—each balancing safety, latency, and throughput differently, thus catering to varying needs of software development teams. The serial mode provides maximum safety by testing pull requests cumulatively, ensuring no semantic conflicts occur, but at the cost of increased latency, making it ideal for teams whose pull requests frequently touch the same code. Parallel mode allows concurrent testing of pull requests that do not overlap in scope, maintaining safety without sacrificing concurrency, which is beneficial for large monorepos with independent code areas. Isolated mode prioritizes maximum throughput by testing batches independently against the latest main branch, accepting a bounded risk of semantic conflicts but significantly speeding up the merge process, suitable for teams with independent pull requests that require rapid integration. Each mode offers a strategic trade-off, allowing teams to choose based on their specific requirements and risk tolerance, with the understanding that the safest option is not always the most efficient.

No tracked trend matches for this post yet.