codex-bot-andresmgsl/ceremony
1
0
Fork 0
forked from heavy-duty/ceremony
Code Pull requests Activity

docs(labels): qualify the instant trigger surface

Browse source
This commit is contained in:
codex-bot-andresmgsl 2026-08-25 00:24:05 +00:00
parent 7690c15e1a
commit 7da89a46aa
1 changed files with 7 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
.github/workflows/labels.yml vendored
View file

@ -21,13 +21,13 @@ name: labels
# one `review_requested` event per panelist per request, so every review
# round displaces runs and the rate scales with panel size. The
# sweep now lives in labels-sweep.yml behind its own caller, and the
# trigger job below is its wake: it fires on every event this caller
# subscribes — the exact surface that used to run reconcile directly — so
# same-repository wake latency (#137) remains seconds-scale, while a displaced
# sweep cancels on the Actions tab, attached to no PR. Fork-headed runs cannot
# dispatch with their read-only token, so their labels arrive on the scheduled
# sweep cadence. PR checks show scope + trigger for same-repository heads, or
# fork_head for fork heads.
# trigger job below is its instant wake: it fires on every issue event and
# same-repository PR event this caller subscribes to, preserving that part of
# the surface that used to run reconcile directly. Same-repository wake latency
# (#137) remains seconds-scale, while a displaced sweep cancels on the Actions
# tab, attached to no PR. Fork-headed runs cannot dispatch with their read-only
# token, so their labels arrive on the scheduled sweep cadence. PR checks show
# scope + trigger for same-repository heads, or fork_head for fork heads.
#
# This cannot loop: the trigger's dispatch and the reconciler's label
# writes both use GITHUB_TOKEN. GitHub does not create workflow runs from