liveBook · Manning

Merge queue wait time

As explained in Vibe Engineering

Merge queue wait time is the elapsed time a pull request waits after passing continuous integration before it is merged.

Merge queue wait time measures how long a pull request waits after passing continuous integration before merging. It exposes bottlenecks that CI speed cannot: review capacity, organizational flow, or conservative approval thresholds. section 10.7.1

A review bottleneck made measurable

Yellow pull requests waited an average of 4.2 hours for review, even though CI was fast. Tracking this metric showed that the constraint had moved from verification to human review, motivating broader use of the Green auto-merge category. section 10.7.1

How Vibe Engineering covers it

How deep it goes
Defines the elapsed interval and interprets it operationally, stopping short of prescribing a universal target.
Examples
Uses Yellow pull requests averaging 4.2 hours and Green auto-merging to illustrate review delay.
What it assumes
Assumes familiarity with continuous integration, pull requests, review queues, and merge decisions.
What you can do after
Diagnose whether review capacity, rather than verification speed, is constraining delivery.
How it connects
Connects continuous integration, pull requests, code review, and automated merging.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Vibe Engineering. The section links point to the parts of the book it draws on.