ci.knotless.dev watches chadtmiller.com/hud by name (KNOTLESS_RUN_REPOS on the infra runner box, KNOTLESS_RUN_DISCOVER empty). When HUD was made public (repo publicize, 09:38 UTC 2026-11-22), its log said:
and it ran nothing of HUD's afterwards. A release workflow asked for at main (knotless run rerun knotless://chadtmiller.com/hud --ref refs/heads/main --workflow release, rerun at://did:plc:bcgltzqazw5tb6k2g3ttenbj/dev.knotless.rerun/3n2kdckpvmnlo.3n2w4xtr6otmx) showed queued on the pages but no runner took it. runner add knotless://chadtmiller.com/hud ci.knotless.dev again did not bring it back. Its state.json still names HUD's pulls by their space URIs (at://did:plc:bcgltzqazw5tb6k2g3ttenbj/space/dev.knotless.space/hud/...).
runner.knotless.dev kept running HUD's checks after the move, so it seems to be the named-repositories path.
How to see it
A runner with a repository in KNOTLESS_RUN_REPOS while it is private, the repository made public, then a push or an asked run on it. Unsure whether runner.knotless.dev survived because it discovers or because it was told again.
What you expected
The runner follows the repository out of its space and keeps watching it; at least, runner add tells a running runner to take it up again, as its description says.
What happened
ci.knotless.dev watches
chadtmiller.com/hudby name (KNOTLESS_RUN_REPOSon the infra runner box,KNOTLESS_RUN_DISCOVERempty). When HUD was made public (repo publicize, 09:38 UTC 2026-11-22), its log said:and it ran nothing of HUD's afterwards. A
releaseworkflow asked for at main (knotless run rerun knotless://chadtmiller.com/hud --ref refs/heads/main --workflow release, rerunat://did:plc:bcgltzqazw5tb6k2g3ttenbj/dev.knotless.rerun/3n2kdckpvmnlo.3n2w4xtr6otmx) showed queued on the pages but no runner took it.runner add knotless://chadtmiller.com/hud ci.knotless.devagain did not bring it back. Itsstate.jsonstill names HUD's pulls by their space URIs (at://did:plc:bcgltzqazw5tb6k2g3ttenbj/space/dev.knotless.space/hud/...).runner.knotless.dev kept running HUD's checks after the move, so it seems to be the named-repositories path.
How to see it
A runner with a repository in
KNOTLESS_RUN_REPOSwhile it is private, the repository made public, then a push or an asked run on it. Unsure whether runner.knotless.dev survived because it discovers or because it was told again.What you expected
The runner follows the repository out of its space and keeps watching it; at least,
runner addtells a running runner to take it up again, as its description says.Where
knotless.dev; ci.knotless.dev (
knotless-ci-run-1, KNOTLESS_COMMIT 025f8ac) on hetzner-infra's infra runner box. Found with the reviewer's missing tree, Reviewer's mirror of a repository made public lacks a tree; its verdict carries forward, from the same publicize.