2026-08-10T18:24:37Z - 2026-09-10T18:24:37Z
Overview
There has not been any commit activity in this period.
3 issues closed from 2 users
Closed
#115 Forgejo Actions runner — make rig workflows execute
Closed
#133 rig forgejo-runner status reports (active) as health — a poller that has gone quiet looks identical to a working runner
Closed
#145 ceremony automation cannot run on Forgejo — the reconcilers are built on gh, which speaks an API Forgejo does not serve
2 issues created by 2 users
Opened
#149 ceremony pin 0.3.0 → 0.6.1 — adopt the Forgejo-capable callers so the reconcilers finally run here
Opened
#150 forgejo-runner install writes no config, so every rig-installed runner is pinned to one job at a time and no operator can change it durably
8 unresolved conversations
Open
#141
forgejo-runner install reports 'installed and running' for a crash-looping unit — Type=simple is active the instant it forks
Open
#142
forgejo-runner install does not check the Docker Engine, and its group warning understates a fatal condition
Open
#143
rig forgejo-runner status says nothing about 'activating' — the one systemd state that always means a crash loop
Open
#148
runuser joins the admin-binary preflight — and runner remove gets the preflight it lacks
Open
#123
templates_archive_urls' Forgejo comment is wrong — the archive/refs/{tags,heads} paths are served
Open
#124
INSTALLED_FROM records no forge, now that RIG_HOST decides which one a tree came from
Open
#127
drill/drill.sh installs rig from GitHub only — the release gate cannot exercise the RIG_HOST channel
Open
#129
drill/drill.sh's runner leg exercises only rig runner — the forgejo-runner family ships with no end-to-end gate