Repository navigation
fix(ci): skip upstream release jobs on fork - #6
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
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.
Issue for this PR
Closes #5
Type of change
What does this PR do?
The fork's
devpush leavesgeneratequeued on an unavailable Blacksmith runner. Thepublishjob also queues because itsalways()condition runs after the upstream-only build jobs are skipped. Opening an issue or PR queues upstream triage and duplicate-check jobs on the same unavailable runner. This PR limits those jobs and the GitHub Action release job toanomalyco/opencode. On the fork, they skip before requesting a runner. Upstream behavior is unchanged.How did you verify your code works?
devrun hasgenerateandpublishqueued on Blacksmith, while Linux tests, typecheck, and Nix evaluation use GitHub runners.Screenshots / recordings
No UI change.
Checklist