jochen
2221be11a6
mesh/merge-gate the mesh is checking this head against every machine
mesh/delivery delivered
Turning the merge check on for every repository showed it asked the wrong questions: a repository chose whether it was checked, the gate mapped a change onto modules its own way, the shared-code rule rebuilt 103 modules for a root script, and nothing kept a commit off the trunk from becoming a module's version. Records the operator's decisions, narrows ADR 0237 decision 4, revises to-be 45 §9 and Phase 5 and to-be 30, closes issue 280's left-open, and gives this repository its own merge-check.sh.
12 lines
548 B
Bash
12 lines
548 B
Bash
#!/bin/sh
|
|
# mesh-check-toolchain: go
|
|
#
|
|
# This repository's own check (ADR 0238): the second layer of a pull request's merge check,
|
|
# `mesh/repo-check`, run by the build seat in the mesh's Go toolchain, which carries Python for it. No
|
|
# module is built from here, so no gate runs (`mesh/merge-gate` says the change touches none). The three
|
|
# checks every merge here must pass (AGENTS.md): the records' structure, the reading order, the cycle.
|
|
set -eu
|
|
python3 00-META/checks/records.py
|
|
python3 00-META/checks/index.py
|
|
python3 00-META/checks/cycle.py
|