Disable weekly CI jobs in forks #455
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
Signed-off-by: Michel Hidalgo <[email protected]>
|
FYI @pvela2017 |
glpuga
approved these changes
Dec 20, 2024
nahueespinosa
approved these changes
Dec 20, 2024
|
Got another spurious |
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.
Proposed changes
It has been recently brought to my attention that our weekly CI jobs are getting run in fork repositories. Users may inadvertently end up in this scenario if they enable GHA workflows on their forks, see https://github.com/orgs/community/discussions/26704.
While I do think it makes sense for plain CI jobs to be available to forks if the owners chooses to, weekly CI jobs seem like a waste of compute. This patch ensures those jobs only run for this repository.
Type of change
Checklist