This repository has been archived by the owner on Jan 22, 2025. It is now read-only.
GitHub workflows: Disable cron schedule for forks #34703
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
yihau
approved these changes
Jan 9, 2024
Forks will run all the cron schedules. And I do not think they benefit from those. For the downstream project checks, these runs are actually very expensive - about an hour of run time per execution. Easily draining free account limits.
joncinque
approved these changes
Jan 9, 2024
|
Fixed the title. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
Forks will run all the cron schedules. And I do not think they benefit from those. For the downstream project checks, these runs are actually very expensive - about an hour of run time per execution. Easily draining free account limits.
Solution
Disable jobs that run on cron schedules, except for the main repo.
I am not 100% sure this is the best solution.
But this is what I was able to figure out base on some online discussions.
I do not think anyone wants to run this in their forks?
But if they do, they would need to carry a local patch.