Design 47: a group's own merge in order asks nothing again (ADR 0395 §1, review)

2026-10-16 13:32:39 +02:00
parent a65e1076a2
commit 91f82cd38e
1 changed files with 2 additions and 1 deletions
@@ -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