Run on the halogen label: the yukart runner is not Android-only

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DDwfd6Ki8UfG4hK6W5YpJz
2026-10-13 01:01:18 +09:00
parent 93e198f85e
commit 667678b9ae
4 changed files with 5 additions and 5 deletions
@@ -37,7 +37,7 @@ fails that push's run: the commit that made two repos disagree is the one marked
 A new repo is checked as soon as it exists in the org; it needs the caller only to
 trigger checks on its own pushes.

- ⚠ **The caller must say `runs-on: flutter-android`.** Gitea hands a reusable-workflow
+- ⚠ **The caller must say `runs-on: halogen`** (the yukart org's runner, `halogen-yukart`). Gitea hands a reusable-workflow
  call to a runner chosen by the *caller's* `runs-on`; the called workflow's own is not
  consulted for that. Without it, the instance-wide `pi5-runner` on the Gitea host takes
  the job, and its jobs see the server as `http://gitea:3000`, which does not resolve.