Gate seeds a never-merged repository's trunk head and follows a retargeted base; gitea announces a retarget and sets a default branch and a pull request's base (issue 1422; group fix/1422-trunk-unknown) #537

Merged

mesh-tools merged 4 commits from fix/1422-trunk-unknown into main 2026-10-28 10:34:47 +00:00

Conversation 1 Commits 4 Files Changed 15

+370 -16

4 Commits

Author	SHA1	Message	Date
jschoubben	f5d4b2f86e	Gate: take a retargeted pull request's new base, so a retarget to main is seeded and asked and one away from main is not (issue 1422) ... A re-announcement updated the base head but never the base: a pull request retargeted from nox-mesh to main stayed 'into nox-mesh' and was never asked or seeded, and one retargeted away from main kept its open ask.	2026-10-28 11:12:21 +01:00
jschoubben	7c2aa0a739	gitea: set a default branch and a pull request's base by named tools; announce a retargeted pull request again (issue 1422)	2026-10-28 11:07:31 +01:00
jschoubben	e057670bc4	Gate: seed source.main from the latest announcement's base head, not the newest delivery's (issue 1422) ... A delivery made earlier can be announced again after a newer one, with main's head moved on: its base_sha is the freshest. The gate now keeps when each base_sha was announced and seeds from the latest.	2026-10-28 11:05:38 +01:00
jschoubben	0c6b7b5d64	Gate: seed source.main with the trunk head of a repository it names none of (issue 1422) ... source.main moved only at a merge, so a repository never merged through the gate had no trunk head and the checker could never judge its pull requests. The gate already hears main's head on each gitea.pull.updated (base_sha); it now adds it for a repository source.main lacks, from the newest open pull request into main, in one compare-and-set write that never replaces a head. A pull request into another base seeds nothing (ADR 0484 §11).	2026-10-28 11:03:40 +01:00