ci: prevent upstream release jobs from running in the fork - #2
Draft
pilprod wants to merge 1 commit into
Draft
Conversation
Signed-off-by: pilprod <51009687+pilprod@users.noreply.github.com>
Owner
Author
|
Validation note: the guarded workflow is tag/manual-release scoped and intentionally does not run for pull requests. All touched workflow YAML parses successfully, |
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
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.
Summary
Restrict every publishing job in the upstream tag workflow to
kagent-dev/kagent.The maintained
pilprod/kagentfork is an evaluated source input and does not own a release lifecycle. Tag pushes or manual dispatches in the fork now skip image, chart, Python package, and GitHub release publication.Validation
git diff --checkpassed.