docs: README install quick start names the Forgejo channel (RIG_HOST)
we can close this PR ? is safe? or some other consideration should be made ?
feat(drill): a forgejo-runner lifecycle leg beside the GitHub one
fix(forgejo-runner): 'active' is not proof the runner is fetching
rig-installed Forgejo runners have their cache server disabled — ProtectHome=read-only vs $HOME/.cache
fix(forgejo-runner): the cache server can start
feat(drill): a forgejo-runner lifecycle leg beside the GitHub one
lets create a 0.3.2 version so i can install an test the forgejo-runner.. also, update the readme so i can see the correct install command -> curl -fsSL https://forgejo.heavyduty.builders/heavy-dut…
Ceremony on Forgejo — align actors and bootstrap the issue-flow taxonomy
fix: align Ceremony actors with Forgejo
fix: align Ceremony actors with Forgejo
fix: align Ceremony actors with Forgejo
Eight core taxonomy labels are absent — the work queue cannot be expressed and needs-ruling cannot be set
The core label taxonomy is incomplete in this repo — the work-queue labels do not exist
.github/labels.conf's panel= names four accounts that do not exist on this instance
.github/labels.conf names panel and triage identities that do not exist on this instance