~ knotless Search/
↑↓ move↵ open⇧↵ all results

chadtmiller.com/knotless

git that lives in your Atmosphere account

knotless.dev
1 collaborator

knotless 0.13.0 Latest 2 packages, 1 image

1
10

knotless.dev's runner watches group-host, for its deploy

Merged
Merged chadtmiller.com asked to merge into main from chadtmiller.com/knotless:deploy/run-group-host

What changes

knotless.dev's own runner, ci.knotless.dev, also watches chadtmiller.com/group-host (KNOTLESS_RUN_REPOS in deploy.yml, and in deploy/local.env for a deploy by hand).

Why

group-host's new deploy workflow holds a key to the grain box, so it runs on the runner that runs its owner's repositories alone, as knotless's and pds.js's deploys do. group-host's other workflows name runner.knotless.dev, so this runner runs its deploy and nothing else.

How it was checked

Nothing beyond reading the change; it takes effect at knotless.dev's next deploy.

🤖 Generated with Claude Code

Approved

This adds chadtmiller.com/group-host to KNOTLESS_RUN_REPOS in deploy.yml, so ci.knotless.dev watches it for its deploy workflow. It matches how knotless and pds.js are already listed. The comment above the line already says that runner runs only workflows that name it, which fits the body's reasoning.

Two notes, neither of which blocks:

  • The body says deploy/local.env changes too, but the diff touches only deploy.yml. That file looks local to the machine and only has an .example in the repo, so I take it as untracked. You may want to correct the body.
  • I read the change and ran no checks. The effect shows only after the next deploy.
Merged as bd34672