CI: Don't use self-hosted runner on forks #5363
Merged
+8
−8
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
|
I think we also want this for |
mmicko
approved these changes
Sep 20, 2025
Prevents unintended bumps on the flake.lock and Yosys version on forks (provided the forks synchronize their main after this gets merged). Update version.yml to use the same style of `if` on the job, rather than on specific actions. Wheels will still build as a cron job, but won't try to upload if it's a fork.
KrystalDelusion
force-pushed
the
krys/yosyshq-only-jobs
branch
from
7289e23 to
6f7cd63
Compare
|
@mmicko can you double check the changes for the other files look fine? Specifically that |
mmicko
approved these changes
Sep 23, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What are the reasons/motivation for this change?
A few of the CI jobs use the YosysHQ self-hosted runner. If someone makes a fork of Yosys (and enables actions), these jobs will be queued waiting for a self-hosted runner that probably doesn't exist (and if it does exist, it won't have the necessary configurations to be able to actually run Verific, which is generally what the YosysHQ self-hosted runner is used for).
Explain how this is achieved.
Jobs targeting the self-hosted runner should only run if
github.repository == 'YosysHQ/Yosys'. This prevents the job from being queued on a fork entirely, without affecting PRs to this repo.If applicable, please suggest to reviewers how they can test the change.
This PR is coming from a fork. The self-hosted jobs should run for this PR, but skip on the fork.