scruffydude/project-awry
Watch
1
0
Fork
You've already forked project-awry
 0
Code Issues Pull requests Projects Releases 22 Packages Wiki Activity Actions

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

Merged
Nimby merged 1 commit from task/76-reuse-act-runner into main 2026-10-05 19:01:16 -04:00
Conversation 0 Commits 1 Files changed 2 +43 -28
Nimby commented 2026-10-05 19:01:15 -04:00
Collaborator
Copy link

Closes #76

  • Workflow: forgejo.* contexts become github.* (server_url, repository, sha, token). Gitea's act_runner, which optibcc already runs, doesn't define forgejo.*; both runners support github.*. The bump input is read as github.event.inputs.bump (empty on push, so it defaults to patch). No behaviour change otherwise.
  • tools/ci/README.md: the primary setup is now "add the godot label to optibcc's existing act-runner" (exact config.yaml labels, with the two existing labels kept verbatim, and force_pull: false for local images). The dedicated forgejo-runner stays as the alternative.

The runner change itself happens on optibcc, outside the repo, followed by a first manual run.

🤖 Generated with Claude Code

Closes #76 - Workflow: `forgejo.*` contexts become `github.*` (`server_url`, `repository`, `sha`, `token`). Gitea's act_runner, which optibcc already runs, doesn't define `forgejo.*`; both runners support `github.*`. The bump input is read as `github.event.inputs.bump` (empty on push, so it defaults to patch). No behaviour change otherwise. - `tools/ci/README.md`: the primary setup is now "add the `godot` label to optibcc's existing act-runner" (exact `config.yaml` labels, with the two existing labels kept verbatim, and `force_pull: false` for local images). The dedicated forgejo-runner stays as the alternative. The runner change itself happens on optibcc, outside the repo, followed by a first manual run. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
optibcc already runs a shared Gitea act_runner, so reuse it with an extra
godot:docker://project-awry-ci:latest label instead of a second runner.
act_runner doesn't define the forgejo.* expression contexts, so the
workflow now uses github.* (supported by both runners) and reads the
dispatch input via github.event.inputs. The README documents the
add-a-label setup, keeping the dedicated forgejo-runner as an alternative.

Closes #76

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Nimby merged commit b146b1d457 into main 2026-10-05 19:01:16 -04:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
scruffydude/project-awry!77
No description provided.