Don't run workflow steps that require secrets on forks #3089
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.
Problem
Since #3085 we run CKAN's CI with GitHub Actions. An advantage of this is that they also run in forked repositories automatically, without the need to set up an external service.
However, this also leads the workflows trying to execute all the deployment steps and the Discord notification, which doesn't make sense in forked repos and will ultimately fail since the secrets needed to run these steps aren't available.
Changes
This PR adds
if
s to all the steps that need secrets to work. Theseif
s check whether the needed secrets are set, and if not, skip the step.Also fixed one network test failing since #3084.