[skip changelog] Disable scheduled workflows that would always fail from running in forks #888
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
rsora
approved these changes
Aug 3, 2020
|
@per1234 Do we want to include the check also for the https://github.com/arduino/arduino-cli/blob/master/.github/workflows/link-validation.yaml workflow? |
These workflows use resources that are only available when run in the arduino/arduino-cli repository, so would always fail when they run in a repository. They are of no value to fork repositories. They are triggered by the schedule event, so they cause regular annoying and confusing workflow failure notifications for every fork owner.
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.
These workflows use resources that are only available when run in the arduino/arduino-cli repository, so would always fail when they run in a repository. They are of no value to fork repositories. They are triggered by the schedule event, so they cause regular annoying and confusing workflow failure notifications for every fork owner.
Please check if the PR fulfills these requirements
before creating one)
Bug fix.
It's extremely annoying to have a fork of this workflow with GitHub Actions workflows enabled because there are multiple workflows that are triggered by
scheduleevents which rely on secrets that are only defined when run in the upstream repository. This causes the fork owner to get lots of notifications of failed workflow runs.Scheduled workflows of no value to contributors are configured to only run when in the
arduino/arduino-clirepository.No.