ci: run checks on the self-hosted tuejon-ci runner - #22
Merged
Merged
Conversation
Move the check job off GitHub-hosted runners onto the repository's own runner, and skip pull requests from forks so outside code never runs there.
TueJon
commented
Sep 19, 2026
TueJon
left a comment
TueJon
left a comment
Owner
Author
There was a problem hiding this comment.
No blocking findings.
The trigger guard keeps fork code off the self-hosted runner while preserving main pushes and same-repository PR checks; the exact-head check steps passed on the new runner labels.
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.
The
checkjob ran onubuntu-latest. It now runs on the repository's own self-hosted runner (tuejon-ci, on VD-FW), in line with the rule that all of our CI runs on our own runners.That runner shares a host with production credentials, so the job skips pull requests from forks. The repository also now requires approval before workflows run for any outside contributor. Fork PRs are still reviewed as before; run the checks after moving a fork branch into the repo if needed.
Validation: this PR's own run exercises the new runner.