3c17b963f3
Forgejo Actions runner on the stage server picks up these jobs. Runs on the same labels `[self-hosted, linux]` — same self-hosted box as the Docker registry and the stage itself. deploy-stage is simplified: no SSH round-trip (runner and stage are the same host), just `cp` + `docker compose pull/up`. POS job kept as-is; it's gated on tag/dispatch and a Windows runner, so on Forgejo it'll simply not match any runner and stay queued — that's fine, POS ships from tags only. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| ci.yml | ||
| deploy-stage.yml | ||
| docker.yml | ||
| notify.yml | ||