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

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

merge-check.sh (TypeScript toolchain): npm ci, typecheck (sources and tests), the unit suite (160 tests). The integration suite and the replays need a lab and the container runtime, which unapproved code is not given: said as not run. Needs git in the TypeScript toolchain (mesh-tools PR) for the last-run test. Tested in the emulated check environment: passes.

`merge-check.sh` (TypeScript toolchain): npm ci, typecheck (sources and tests), the unit suite (160 tests). The integration suite and the replays need a lab and the container runtime, which unapproved code is not given: said as not run. Needs git in the TypeScript toolchain (mesh-tools PR) for the last-run test. Tested in the emulated check environment: passes.
mesh-admin added 1 commit 2026-10-06 20:51:41 +00:00
A merge-check.sh, the repository's layer of the mesh's merge check (mesh/repo-check), in
the TypeScript toolchain: install from the lock file, type-check, the unit suite. The
integration suite and the replays need a lab and the container runtime, which unapproved
code is not given: said as not run, never passed silently.
mesh-admin merged commit bc3709a66a into main 2026-10-06 21:00:38 +00:00
mesh-admin deleted branch feat/a-merge-check-of-its-own 2026-10-06 21:00:38 +00:00
Author
Contributor

Delivery novox/mesh-lab@a4f6bb8ce054 — held since 2026-10-06T23:05:27Z

Held for a person: merged without a passing check: only a person decides that it goes on — mesh-delivery.release with why lets it go on.

Delivery plan — builds nothing: the change touches no module of the mesh's graph

Transitions

  • 2026-10-06 23:05 (new) → proposed (announced): novox/mesh-lab#53 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

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

<!-- mesh-delivery:view --> **Delivery** `novox/mesh-lab@a4f6bb8ce054` — **held** since 2026-10-06T23:05:27Z Held for a person: merged without a passing check: only a person decides that it goes on — `mesh-delivery.release` with why lets it go on. **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-06 23:05 (new) → proposed (announced): novox/mesh-lab#53 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 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
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-lab#53