• Joined on 2026-07-19
andres commented on issue heavy-duty/rig#144 2026-08-01 21:10:25 +00:00
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

andres commented on issue heavy-duty/rig#145 2026-08-01 19:36:29 +00:00
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…

andres closed issue heavy-duty/rig#136 2026-07-31 21:24:06 +00:00
test/cli.sh is not hermetic — 13 checks fail on any box that has a Forgejo runner installed
andres pushed to main at heavy-duty/rig 2026-07-31 21:24:06 +00:00
9cb81c9f6b Merge pull request 'test: cli.sh reads fixtures, not the host it happens to run on' (#137) from build/136-cli-hermetic into main
7385707770 test: the third hermetic pin can actually fail
d46697034d test: pin the hermeticity, not just achieve it
fd5c04efc9 test: cli.sh reads fixtures, not the host it happens to run on
Compare 4 commits »
andres merged pull request heavy-duty/rig#137 2026-07-31 21:24:04 +00:00
test: cli.sh reads fixtures, not the host it happens to run on
andres pushed to main at heavy-duty/rig 2026-07-31 21:18:00 +00:00
0524f288c3 Merge pull request 'docs: README install quick start names the Forgejo channel (RIG_HOST)' (#132) from build/131-readme-forgejo-install into main
4b9de4818f docs: Forgejo dev-tree line beside the release one — the family lives on main until 0.3.2 tags
47aaeda319 docs: README install quick start names the Forgejo channel (RIG_HOST)
Compare 3 commits »
andres merged pull request heavy-duty/rig#132 2026-07-31 21:17:59 +00:00
docs: README install quick start names the Forgejo channel (RIG_HOST)
andres closed issue heavy-duty/rig#131 2026-07-31 21:17:59 +00:00
README's install quick start has no Forgejo channel — RIG_HOST shipped in #111 and is documented nowhere
andres commented on pull request heavy-duty/rig#132 2026-07-31 20:57:43 +00:00
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 ?

andres pushed to main at heavy-duty/rig 2026-07-31 20:56:19 +00:00
86b749876a Merge pull request 'feat(drill): a forgejo-runner lifecycle leg beside the GitHub one' (#130) from build/129-forgejo-runner-drill-leg into main
9afcdf858f fix(drill): the leg row is the whole lifecycle, not just the job
e42ba31a09 fix(drill): the pre-dispatch baseline folds max too, and the suite is hermetic
9c0e508b76 fix(drill): read every task, and fail a configured leg that cannot mint
1179d3142f feat(drill): a forgejo-runner lifecycle leg beside the GitHub one
Compare 5 commits »
andres merged pull request heavy-duty/rig#130 2026-07-31 20:56:18 +00:00
feat(drill): a forgejo-runner lifecycle leg beside the GitHub one
andres pushed to main at heavy-duty/rig 2026-07-31 20:55:20 +00:00
306844daa8 Merge pull request 'fix(forgejo-runner): 'active' is not proof the runner is fetching' (#134) from build/133-status-active-is-not-health into main
848e3f42ef test(forgejo-runner): drive the liveness note's state boundary
1daf7004d7 fix(forgejo-runner): 'active' is not proof the runner is fetching
Compare 3 commits »
andres merged pull request heavy-duty/rig#134 2026-07-31 20:55:19 +00:00
fix(forgejo-runner): 'active' is not proof the runner is fetching
andres closed issue heavy-duty/rig#135 2026-07-31 20:35:34 +00:00
rig-installed Forgejo runners have their cache server disabled — ProtectHome=read-only vs $HOME/.cache
andres pushed to main at heavy-duty/rig 2026-07-31 20:35:34 +00:00
ce43c021a5 Merge pull request 'fix(forgejo-runner): the cache server can start' (#138) from build/135-runner-cache-dir into main
a45d84892f fix(forgejo-runner): the cache server can start
Compare 2 commits »
andres merged pull request heavy-duty/rig#138 2026-07-31 20:35:33 +00:00
fix(forgejo-runner): the cache server can start
andres commented on pull request heavy-duty/rig#130 2026-07-30 23:45:21 +00:00
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…

andres commented on pull request heavy-duty/rig#130 2026-07-30 23:43:07 +00:00
feat(drill): a forgejo-runner lifecycle leg beside the GitHub one

what is happening ?

andres closed issue heavy-duty/rig#116 2026-07-30 22:57:20 +00:00
Ceremony on Forgejo — align actors and bootstrap the issue-flow taxonomy
andres pushed to main at heavy-duty/rig 2026-07-30 22:57:20 +00:00
4a6e9761e5 Merge pull request 'fix: align Ceremony actors with Forgejo' (#128) from codex-reviewer-andresmgsl/rig:build/116-forgejo-actors into main
7aca642ba5 fix: preserve triage across both forges
0362e5cf43 fix: align Ceremony actors with Forgejo
Compare 3 commits »