From b0cd4c9101862ad958fbbb46ca449670b51aed17 Mon Sep 17 00:00:00 2001 From: Kyle Sexton <153232337+kyle-sexton@users.noreply.github.com> Date: Wed, 28 Oct 2026 22:55:33 -0400 Subject: [PATCH] perf(pr-pipeline): raise merge.max-in-flight from 5 to 10 One full run of main's tip verifies every lane merge it contains, so a higher cap arms more lane PRs per verification cycle without adding full runs. The lane cleared about 5 PRs per 55 minutes at a cap of 5 against 13 or more new lane PRs an hour. Co-Authored-By: Claude Opus 5.5 --- .changes/pr-pipeline/perf-max-in-flight-10-5b1c7e2a.md | 7 +++++++ docs/conventions/pr-pipeline.yaml | 2 +- 2 files changed, 8 insertions(+), 1 deletion(-) create mode 100644 .changes/pr-pipeline/perf-max-in-flight-10-5b1c7e2a.md diff --git a/.changes/pr-pipeline/perf-max-in-flight-10-5b1c7e2a.md b/.changes/pr-pipeline/perf-max-in-flight-10-5b1c7e2a.md new file mode 100644 index 0000000000..d879329b74 --- /dev/null +++ b/.changes/pr-pipeline/perf-max-in-flight-10-5b1c7e2a.md @@ -0,0 +1,7 @@ +--- +bump: patch +--- + +### Changed + +- This repository's `merge.max-in-flight` rises from 5 to 10. One full run of main's tip verifies every lane merge it contains, so the lane arms up to twice as many pull requests per verification cycle with no extra full runs. A red run now charges up to 10 unverified lane merges, and any charge still demotes the rung. diff --git a/docs/conventions/pr-pipeline.yaml b/docs/conventions/pr-pipeline.yaml index f3582159c3..2de469efae 100644 --- a/docs/conventions/pr-pipeline.yaml +++ b/docs/conventions/pr-pipeline.yaml @@ -958,7 +958,7 @@ merge: # Lane merges in flight at once (queued plus merged and not yet verified). # The merge queue tests each PR against the latest base plus the PRs ahead # of it. - max-in-flight: 5 + max-in-flight: 10 # Paths the PR checks read (git pathspecs). When main changed one since a # PR's merge base, the gate updates the PR from main instead of enqueuing # it, and a later run enqueues the new head once its checks pass: a head