4 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	6556e61485	Read a pull request's review record again when its description is edited, and ask the Approve again if it was unanswered (issue 1079)	2026-10-18 01:12:40 +02:00
jschoubben	668444785d	Ask the Approve as soon as the checks pass, with no ready mark (issue 1022) ... The review finishes before the push and its record is a Reviewed-by line in the description, so the mark repeated what the push meant. mesh-delivery asks the operator when a pull request's checks pass, keeps an ask through a trunk move by asking the check again at once, and hands the merge tool the approved heads, which replace the forge review of each sibling.	2026-10-17 20:44:54 +02:00
jschoubben	2833a049aa	Make the forge's webhook a system one, and say whether its events are heard (hq issue 729) ... POST /admin/hooks on gitea 1.27.3 makes a default webhook unless config.is_system_webhook is "true": a default webhook fires for no existing repository, and the system listing does not name it, so every start made another and no event reached the receiver. Its edit never changes a secret or a kind, so the new system webhook is made first and read back, then every other hook at the receiver is deleted: system, default, and each repository's copy of a default one, which would send its events twice. gitea_events says where the receiver listens, the hook as ensured and what it replaced, the verified and refused deliveries and the polls' pace. When nothing verified for ten minutes, since the start or the last delivery, while the poll found two heads or merges no event said, it is logged loudly once per silent spell and answered unhealthy; so are deliveries refused since the last verified one.	2026-10-14 23:28:41 +02:00
jschoubben	1d8a244ba4	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