Cite the hq issues by the numbers they were given: 285, 286, 287
mesh/delivery held for a person: merged, and the controller opened no walk for it within 10m0s — nothing it holds follows that branch, or the merge was…
mesh/merge-gate pass: builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step; every machine composes with the change as it…
mesh/repo-check pass: its merge-check.sh passed

(cherry picked from commit 8bf7026d97)
This commit is contained in:
jochen
2026-10-08 01:42:22 +02:00
parent 6ea457df74
commit 56b206fe04
7 changed files with 16 additions and 16 deletions
+2 -2
View File
@@ -64,7 +64,7 @@ type Facts struct {
Edges []Edge `json:"edges,omitempty"`
// Beside is the ref each repository is cloned at beside a merge check, by the directory it is found
// under — the commits the mesh runs, the catalogue's main — so a check run by hand reads the siblings
// the build seat reads (novox/hq issue 283).
// the build seat reads (novox/hq issue 286).
Beside map[string]string `json:"beside,omitempty"`
}
@@ -85,7 +85,7 @@ type Versions struct {
// Toolchains are the toolchain images a merge check runs in, by language, as the mesh holds them —
// with no address: the artifact store the snapshot is read from is where they are pulled from. What
// a repository's merge-check.sh runs in on the build seat, and so what it must run in anywhere else
// (novox/hq issue 283): two releases of one compiler disagree, down to how gofmt lays out a file.
// (novox/hq issue 286): two releases of one compiler disagree, down to how gofmt lays out a file.
Toolchains map[string]string `json:"toolchains,omitempty"`
}