Skip to content

workflows: run release artifact build checks from ci.yaml - #4398

Merged
rickeylev merged 1 commit into
bazel-contrib:mainfrom
rickeylev:separate_ci_build_workflow
Nov 1, 2026
Merged

rickeylev merged 1 commit into
bazel-contrib:mainfrom
rickeylev:separate_ci_build_workflow

Conversation

@rickeylev

Copy link
Copy Markdown
Collaborator

Release workflows should not trigger directly on pull request or push
events; CI checks belong in the CI workflow.

Remove the pull_request trigger from release_build_artifacts.yaml,
make its workflow_call ref input optional, and invoke it as a
reusable workflow job from ci.yaml.

Release workflows should not trigger directly on pull request or push
events; CI checks belong in the CI workflow.

Remove the `pull_request` trigger from `release_build_artifacts.yaml`,
make its `workflow_call` `ref` input optional, and invoke it as a
reusable workflow job from `ci.yaml`.
@rickeylev
rickeylev requested a review from aignas as a code owner November 1, 2026 20:20
@rickeylev

Copy link
Copy Markdown
Collaborator Author

AI Disclosure: This PR was created with assistance from a semi-autonomous (human-guided) AI coding agent. The human author directed the design and reviewed the changes. Comments on this PR will be handled with human oversight: the human author reviews and approves any agent-drafted responses or changes before they are posted, or replies directly.

This is an automatically generated agent comment.

@rickeylev
rickeylev merged commit 95347ca into bazel-contrib:main Nov 1, 2026
13 checks passed
@rickeylev
rickeylev deleted the separate_ci_build_workflow branch November 1, 2026 20:43
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