ci: add the CI_RUNS_ON escape hatch to the merge-gating workflow(s) - #128
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the
CI_RUNS_ONescape hatch to the workflow(s) in this repo that gatemerges and have no side effects:
This turns nothing on.
CI_RUNS_ONis left unset here and everywhere, sothe expression resolves to
ubuntu-latestand behaviour is byte-for-byteunchanged. What it buys is the option: when a self-hosted runner is available,
this repo's merge gate can be pointed at it with one API call and pointed back
with one more, instead of needing a workflow edit and a PR first. The account's
hosted Actions minutes are exhausted and every hosted job is currently refused,
so that option is the difference between a real CI verdict and none.
claude-workspaceandmathnasium-session-notesalready carry this line; thisspreads it to the merge-gating subset only.
Deliberately NOT changed: any workflow that deploys, publishes, releases,
uploads an artifact, posts anywhere, or uses a credential or secret. Pointing
those at a container on a personal machine is a security decision, not a
one-line change, and it was not taken here.
How to use it, and the two-variant runner recipe it pairs with:
modules/git-proxy/references/ephemeral-runner.mdin claude-workspace.🤖 Generated with Claude Code
https://claude.ai/code/session_01C3uaCzCK58XoamXHTcCCyh