fix(ci): use fallback runner if there is any sort of error #592
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
no reason to block CI if there is any sort of problem, self-hosted runners are purely a nice to have and should never block really
mikehardy
force-pushed
the
self-hosted-runner-fallback-on-error
branch
from
a78e997 to
da3e1b5
Compare
Member
Author
|
I'm going to merge this one - one of my goals with the self-hosted runner thing is that it never ever ever blocks anything, it needs to be purely a "nice to have" / "if available" from config to execution or it's a fail in my opinion. This should get it there |
david-allison
approved these changes
Oct 28, 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.
no reason to block CI if there is any sort of problem, self-hosted runners are purely a nice to have and should never block really
uses this commit from the PR I'm trying to get merged upstream:
jimmygchen/runner-fallback-action@b016527
but since there is no merge activity in that runner selection action, it's running off the PR branch on my fork 🤷