Design 47: a move of the trunk asks every active check again (ADR 0395) #381

Merged
mesh-tools merged 6 commits from design/47-recheck-on-trunk-move into main 2026-10-16 17:35:53 +00:00
Showing only changes of commit 91f82cd38e - Show all commits
@@ -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