Graphite has introduced a new batch merging feature for its merge queue system, designed to enhance throughput and reduce Continuous Integration (CI) costs for teams using the platform. This feature allows multiple pull requests (PRs) to be grouped together into a single temporary PR, running CI on the batch and merging it collectively if the tests pass, thus optimizing the merge process without slowing down releases or inflating CI costs. Batch merging is effective for managing a higher volume of PRs and can be customized for each repository's desired throughput. Unlike the Parallel CI strategy that ensures every individual PR passes CI, batch merging trades off the need for every single commit to build correctly for faster queue times and reduced CI expenses, while still ensuring that all tests pass at the head of the trunk branch post-merge. In case of a CI failure, options include removing the entire batch or bisecting to identify the problematic PR, with bisecting functionality being developed. Currently, the batch merging feature is available in public beta and can be enabled in merge queue settings.