An approved merge into a repository nothing is built from asks its modules' first builds (issue 1146) #386

Merged

mesh-tools merged 5 commits from fix/1146-first-build-of-new-repo into main

2026-10-18 22:32:42 +00:00

Author	SHA1	Message	Date
jschoubben	e621e15d2f	Its comment names D18 too (issue 1146) mesh/merge-gate head e621e15d2f5d merged into trunk b1cfb85f86ed — pass: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; every … Details mesh/repo-check head e621e15d2f5d merged into trunk b1cfb85f86ed — pass: its merge-check.sh passed Details mesh/delivery delivered Details	2026-10-19 00:20:31 +02:00
jschoubben	a08498b240	Name the waiting first merge's probe D18: designs 06 and 54 already name probe D17 (issue 1146)	2026-10-19 00:20:20 +02:00
jschoubben	39ae7de6d3	Say a first merge that waits past ten minutes for mesh-delivery's word, with probe D17 (issue 1146, AC8)	2026-10-19 00:19:03 +02:00
jschoubben	4e12fc19b7	A first merge into a new repository waits kept for mesh-delivery's word, and the word's arrival asks the builds, with no timer; AC7 on the bus in both orders (issue 1146)	2026-10-19 00:16:36 +02:00
jschoubben	19f15d8ea0	A merge on the operator's Approve into a repository the mesh builds nothing from asks the first build of the modules it holds (issue 1146, AC6, AC7)	2026-10-19 00:11:52 +02:00