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

..

announce.test.ts

issue 976: the forge's announcements get a deterministic message id; the announcement files go, the poll's watermark is kept in the module's state

2026-10-17 13:52:47 +02:00

announcing.test.ts

Ask the Approve as soon as the checks pass, with no ready mark (issue 1022)

2026-10-17 20:44:54 +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

2026-10-12 12:20:23 +02:00

guard.test.ts

Ask the Approve as soon as the checks pass, with no ready mark (issue 1022)

2026-10-17 20:44:54 +02:00

no-ready-mark.test.ts

Ask the Approve as soon as the checks pass, with no ready mark (issue 1022)

2026-10-17 20:44:54 +02:00

pages.test.ts

Name the package each controller-repository image compiles, and say a renamed file under both names (hq ADR 0267, issue 363)

2026-10-10 02:58:31 +02:00

paging.test.ts

Page the announcer through every open pull request updated since its last look

2026-10-12 20:52:27 +02:00

protection-read.test.ts

Read branch protection as the forge's administrator, so builds register again

2026-10-15 00:18:39 +00:00

protection.test.ts

Main takes no push and only mesh-tools merges, set by setup and guarded (issue 948, ADR 0398 §2)

2026-10-16 21:28:43 +02:00

pulls.test.ts

Say where a pending merge check is: queued since when, then building on which machine (hq issue 446)

2026-10-11 03:14:06 +02:00

rule-cases.json

guard.ts: cover every branch for a rule Go's regexp reads otherwise, and hold both matchers to one table (issue 539)

2026-10-12 12:51:22 +02:00

secret-setting.test.ts

Keep every password, token and API key the vault's, never a setting (hq issue 342)

2026-10-13 07:32:19 +02:00

siblings.test.ts

Ask the Approve as soon as the checks pass, with no ready mark (issue 1022)

2026-10-17 20:44:54 +02:00

teams.test.ts

lab: a read-only forge account of its own, and no credential left on disk after a stop (hq issue 624, review 196)

2026-10-13 14:00:59 +02:00

token.test.ts

Main takes no push and only mesh-tools merges, set by setup and guarded (issue 948, ADR 0398 §2)

2026-10-16 21:28:43 +02:00

tools-account.test.ts

Ask the Approve as soon as the checks pass, with no ready mark (issue 1022)

2026-10-17 20:44:54 +02:00

trunk.test.ts

Give the build agent a judge cache of its own, and prove a release branch's move puts its verdicts out of date

2026-10-14 13:48:30 +00:00

webhook.test.ts

Ask the Approve as soon as the checks pass, with no ready mark (issue 1022)

2026-10-17 20:44:54 +02:00