ci: skip scheduled and release workflows on forks #8719
+18
−0
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.
Description
Prevent GitHub Actions workflows that rely on repository secrets or publishing permissions from running on forks. A lot of daily/weekly email spam from failed workflows on forks that are missing the secrets...
This change updates multiple workflows so they only run when the repository is
continuedev/continueby adding a guard just like in https://github.com/continuedev/continue/blob/main/.github/workflows/cla.yaml#L17-L18:This ensures that scheduled tasks, release automation, metrics collection, and dependency submission workflows do not run (and fail) on contributor forks, while preserving all existing behavior for the main repository.
Workflows updated include:
@continuedev/config-yaml@continuedev/fetch@continuedev/llm-info@continuedev/openai-adaptersFixes #8662.
Tests
continuedev/continue