chore(ci): move trusted workflows to RunsOn - #1910
Conversation
Route every GitHub-hosted ubuntu-latest job to a RunsOn 2cpu-linux-x64 runner, namespaced per workflow run. Five enclave-ci jobs keep their dedicated runner group, and the release binary matrix keeps its per-OS routing.
crisp_unit shards its label by test-suite so parallel legs cannot share a runner. The release binary matrix keeps the macos-latest leg GitHub-hosted because RunsOn cannot launch macOS runners, and labels the linux leg for RunsOn.
|
@auryn-macmillan is attempting to deploy a commit to the Gnosis Guild Team on Vercel. A member of the Team first needs to authorize it. |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. 🗂️ Base branches to auto review (2)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Team Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Fork pull requests run untrusted code, so they stay on GitHub-hosted runners; same-repo events use RunsOn. Labels now embed run id, attempt, and job name so concurrent jobs cannot share a runner.
hmzakhalid
changed the title
|
We should perhaps have this PR target a different branch now? |
1e2c0cd
into
theinterfold:feat/avail-vectorx-data-availability
2 participants
Quick PR to move the github workflows to runs-on to see if they go faster there.