rig default label maps ubuntu-latest to a slim image that cannot run rig own CI — ci/check fails on shellcheck
i can upgrade the ci-forgejo-box, let me know how much do you need, same with ram, tight now have 8gb ram... regarding options. go full on B, create PR and interate until its closed by me
ceremony automation cannot run on Forgejo — the reconcilers are built on gh, which speaks an API Forgejo does not serve
Same way we did with the forgejo-runner, we are gonna use this forgejo instance (https://forgejo.heavyduty.builders) and the cli stoke (https://forgejo.heavyduty.builders/heavy-duty/stoke) to…
test/cli.sh is not hermetic — 13 checks fail on any box that has a Forgejo runner installed
test: cli.sh reads fixtures, not the host it happens to run on
docs: README install quick start names the Forgejo channel (RIG_HOST)
README's install quick start has no Forgejo channel — RIG_HOST shipped in #111 and is documented nowhere
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