novox/mesh-controller
13
0
Fork 0
Code Issues Pull Requests 4 Releases Wiki Activity

Review of issue 977: keep the plan's own order for its gates, hold a group only for a composed mesh-delivery, keep mark-ready one release, compare with the batch's start, fail a lone cycle (issue 977)

Browse Source
This commit is contained in:
jschoubben
2026-10-17 21:37:37 +02:00
parent aac4bae5a4
commit 07b050790e
14 changed files with 259 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files
internal/link/build.go
+2 -1
View File
@@ -148,7 +148,8 @@ type CheckRequest struct {
// 0406 §4): with the head, what the pull request's key says the current check is for, and what a waiting request
// is dropped by and a running check stopped by when the key moves.
Trunk string `json:"trunk,omitempty"`
// Ready says the pull request is marked ready (ADR 0406 §3): its check is queued before every other check.
// Ready says mesh-delivery wants this check queued before every other check (ADR 0406 §3); there is no ready mark
// any more (issue 1022).
Ready bool `json:"ready,omitempty"`
// Composed says the pull request is a member of a delivery group whose gate is the composed check's (novox/hq ADR
// 0403 clause 1): this check runs the repository's own merge-check.sh alone, and its gate layer is not run.