mesh-catalog

Files

T

jschoubben 1d8a244ba4

mesh/merge-gate out of date: judged against trunk 2edef5a00ae0, the trunk is now 0e7d9e74d22a; judged again on a recheck or when it is merged

Details

mesh/repo-check out of date: judged against trunk 2edef5a00ae0, the trunk is now 0e7d9e74d22a; judged again on a recheck or when it is merged

Details

mesh/delivery covered after its stop: a later walk that contains it was delivered: plan-1792011830935225963 (novox/mesh-catalog at 0361c44a into main, do…

Details

Say every forge event on the bus through a signed system webhook, and announce a head or merge at once (novox/hq issue 729)

The gitea module keeps one system webhook for every event family, made or
corrected at start with the admin account (POST /admin/hooks, forge 1.27.3)
and a secret it mints and keeps. Its receiver, at the docker bridge's
gateway, refuses an unsigned request before reading it, a body over 5 MB,
and a signature that does not verify; it answers a verified delivery at once,
drops one already heard by its delivery id, and publishes each as
forge.<kind>.<action> on the module's events (its own stream, ADR 0363,
follows issue 725). A pull request opened, pushed to or merged is announced
at once. The polls look every five minutes only while deliveries arrive, and
every 30 s again, saying so loudly, when one finds what no event said or ten
minutes pass without a delivery. The announced records keep both paths from
announcing twice.

2026-10-14 22:21:22 +02:00

announcing.test.ts

Count a ready mark only from a listed account, after the last push and the label (issue 722)

2026-10-14 21:45:39 +02:00

checks.test.ts

Cover a held merge only when the forge says a later delivered merge contains it (review of #150 )

2026-10-09 02:57:18 +02:00

delivery.test.ts

Put the merge check back to pending before a recheck asks it (hq issue 305)

2026-10-08 10:11:26 +02:00

gate.test.ts

Route a recheck's pending through the gitea module's one writer of mesh/merge-gate