Run playtest releases on optibcc's existing act-runner #76

New issue

Closed

opened 2026-10-05 19:00:13 -04:00 by Nimby · 0 comments

Nimby commented

2026-10-05 19:00:13 -04:00

Collaborator

optibcc already runs a shared Gitea act_runner (v0.6.1). Reuse it by adding a godot:docker://project-awry-ci:latest label, instead of a second runner. The workflow uses forgejo.* contexts, which act_runner doesn't define, so switch to github.* (supported by both runners). Document the add-a-label setup in tools/ci/README.md, keeping the dedicated forgejo-runner as the alternative.

optibcc already runs a shared Gitea act_runner (v0.6.1). Reuse it by adding a `godot:docker://project-awry-ci:latest` label, instead of a second runner. The workflow uses `forgejo.*` contexts, which act_runner doesn't define, so switch to `github.*` (supported by both runners). Document the add-a-label setup in tools/ci/README.md, keeping the dedicated forgejo-runner as the alternative.

Nimby self-assigned this

2026-10-05 19:00:13 -04:00

Nimby referenced this issue from a pull request that will close it,

2026-10-05 19:01:15 -04:00

Run playtest releases on optibcc's existing act-runner #77

Nimby closed this issue

2026-10-05 19:01:16 -04:00

Nimby referenced this issue from a commit

2026-10-05 19:01:16 -04:00

Run playtest releases on optibcc's existing act-runner