Repository navigation
ci: let the runner pool route jobs via CI_* variables - #16
Conversation
Both CI jobs now read their runner labels from the CI_LINUX repository variable written by the runner-pool controller. When the variable is unset (for example on fork pull requests) they fall back to ubuntu-latest, the label they use today. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
What changed
.github/workflows/ci.yml: theruns-onof both jobs (offline,packed-consumers) now reads theCI_LINUXrepository variable that the runner-pool controller writes:2
runs-onlines changed, plus a one-line comment. Job names, steps, permissions and triggers are untouched.Behaviour when the variable is unset
Unchanged: the literal default is
ubuntu-latest, the label the jobs use today. This applies wherevervarsis empty, for example on pull requests from forks.Jobs left alone
None; this workflow only has these two jobs.
🤖 Generated with Claude Code
Summary by CodeRabbit