GitHub CI: Skip the manifest update job on forks #13278
Merged
Conversation
This file contains 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
cr7pt0gr4ph7
deleted the
ready-for-merge/disable-netlify-build-for-forks
branch
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.
The steps of manifest update job are already skipped on forks because they do not have the necessary secrets configured, so we skip the job altogether for any repository that is not the main
mixxxdj/mixxxrepository to avoid unnecessary noise in the build log (as well as some issues related to canceling build jobs).It would be preferable to directly check for the presence of the secrets in
jobs.<job_id>.if, but that is not possible, as per actions/runner#520.