---
title: "Skip intermediate results during bisection"
date: 2026-10-20
tags:
  - "Merge Queue"
description: "skip_intermediate_results now saves CI time when a failing batch is split to find the pull request at fault, and the merge queue Stats page shows what the option saves your queue, or would save it."
---

A failing batch is the slow path of a merge queue: Mergify splits it into sub-batches and tests them to find the pull request at fault. With [skip_intermediate_results](https://docs.mergify.com/merge-queue/batches/#skip-intermediate-results-anti-flake-protection) on, a sub-batch that passes now carries the sub-batches before it to merge, since it was tested on top of their changes. They merge without waiting for their own CI, one that failed on a flaky test merges instead of being split again and retested, and the sub-batch that really fails is caught without waiting on the CI still running ahead of it.

The merge queue Stats page now shows, per queue, what the option does for you:

- **Merged on a Later Batch's Pass**: the share of your merged batches the option merged early, and how many of them it merged during speculative checks or during a bisection.
- **Would Have Merged on a Later Batch's Pass**: on a queue without the option, the batches it would have merged early, how long they waited for their own CI instead, and how many of those runs failed and sent the batches behind them back to CI.
To get it, set `skip_intermediate_results: true` in the `merge_queue` section of your configuration. The Stats page needs nothing turned on, so if you have been weighing the option, it now tells you what it would have saved your queue.