From 91f82cd38eff185eec72c6e81ecc58fc42d5d009 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 16 Oct 2026 13:32:39 +0200 Subject: [PATCH] =?UTF-8?q?Design=2047:=20a=20group's=20own=20merge=20in?= =?UTF-8?q?=20order=20asks=20nothing=20again=20(ADR=200395=20=C2=A71,=20re?= =?UTF-8?q?view)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- 03-DESIGN/01-to-be/47-delivery-from-commit-to-delivered.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/03-DESIGN/01-to-be/47-delivery-from-commit-to-delivered.md b/03-DESIGN/01-to-be/47-delivery-from-commit-to-delivered.md index b64a829d..eabe0ca1 100644 --- a/03-DESIGN/01-to-be/47-delivery-from-commit-to-delivered.md +++ b/03-DESIGN/01-to-be/47-delivery-from-commit-to-delivered.md @@ -401,7 +401,8 @@ its author's next push asks its check. A pull request has at most one check at a waiting or running, is dropped or ended when a newer one is asked for it, as a new head already ends its old head's check (issue 726). The build queue keeps delivery builds first; then checks of pull requests marked ready, then the rest, the most recently pushed first. A pull request with no push and no ready mark for 7 days is left out until a -push, a ready mark or a recheck wakes it. A recheck also takes a delivery that is still proposed (issue 888). +push, a ready mark or a recheck wakes it. A recheck also takes a delivery that is still proposed (issue 888). A move made by a delivery group's own member merging in the group's order asks neither the +group's composed check nor its other members again (ADR 0323 ยง6). ## What every transition does