A merge check of its own (hq ADR 0238) #4

Merged
mesh-admin merged 1 commits from feat/a-merge-check-of-its-own into master 2026-10-06 21:00:50 +00:00
Contributor

merge-check.sh (Go toolchain, which carries Python once mesh-tools-go's PR is held): every Python file the service image ships, parsed (no .pyc written). The service is not started (its dependencies are the image's); no tests exist. Tested emulated: passes.

`merge-check.sh` (Go toolchain, which carries Python once mesh-tools-go's PR is held): every Python file the service image ships, parsed (no .pyc written). The service is not started (its dependencies are the image's); no tests exist. Tested emulated: passes.
mesh-admin added 1 commit 2026-10-06 20:51:54 +00:00
The repository's layer of the mesh's merge check (mesh/repo-check): every Python file
the image ships, parsed; what cannot run is said.
mesh-admin merged commit c0ea2c949c into master 2026-10-06 21:00:50 +00:00
mesh-admin deleted branch feat/a-merge-check-of-its-own 2026-10-06 21:00:50 +00:00
Author
Contributor

Delivery jschoubben/f1-circuits@101bf2e040f4 — delivered since 2026-10-06T23:05:28Z

Machines

  • f1-circuits on ace: passed — healthy 3 times over 3m5s
  • f1-circuits on the rest running it: sent

Transitions

  • 2026-10-06 23:05 (new) → proposed (announced): jschoubben/f1-circuits#4 merged; its head was not heard by this owner, so it is made from the forge's word
  • 2026-10-06 23:05 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on
  • 2026-10-06 23:05 held → delivering (go): its walk started on a word that was not this owner's: the controller's own path, which waits for nobody, or a person's plans go
  • 2026-10-06 23:05 delivering → delivered (done): its walk is done: every machine of its deploy plan passed, or was left as its policy says

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

<!-- mesh-delivery:view --> **Delivery** `jschoubben/f1-circuits@101bf2e040f4` — **delivered** since 2026-10-06T23:05:28Z **Machines** - f1-circuits on ace: passed — healthy 3 times over 3m5s - f1-circuits on the rest running it: sent **Transitions** - 2026-10-06 23:05 (new) → proposed (announced): jschoubben/f1-circuits#4 merged; its head was not heard by this owner, so it is made from the forge's word - 2026-10-06 23:05 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on - 2026-10-06 23:05 held → delivering (go): its walk started on a word that was not this owner's: the controller's own path, which waits for nobody, or a person's `plans go` - 2026-10-06 23:05 delivering → delivered (done): its walk is done: every machine of its deploy plan passed, or was left as its policy says The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
Sign in to join this conversation.
No Reviewers
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: jschoubben/f1-circuits#4