Skip to content

ci: prevent upstream release jobs from running in the fork - #2

Draft
pilprod wants to merge 1 commit into
mainfrom
agent/governance-compliance-20260822
Draft

ci: prevent upstream release jobs from running in the fork#2
pilprod wants to merge 1 commit into
mainfrom
agent/governance-compliance-20260822

Conversation

@pilprod

@pilprod pilprod commented Aug 23, 2026

Copy link
Copy Markdown
Owner

Summary

Restrict every publishing job in the upstream tag workflow to kagent-dev/kagent.

The maintained pilprod/kagent fork 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

  • Parsed every workflow YAML file.
  • git diff --check passed.
  • No image, chart, package, tag, or release was created.

Signed-off-by: pilprod <51009687+pilprod@users.noreply.github.com>

pilprod commented Aug 23, 2026

Copy link
Copy Markdown
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, git diff --check passes, and the remote diff contains only repository-identity guards. This PR remains draft; no image, chart, package, tag, or GitHub release was created.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant