Remove duplicate pull_request trigger from operator-ci workflow #2185
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
Fixes duplicate operator e2e test runs by removing conflicting workflow triggers.
Problem
The operator e2e tests were running multiple times on PRs because:
operator-ci.ymlworkflow had a directpull_requesttrigger fordeploy/charts/operator-crds/**workflow_callfromrun-on-pr.ymlSolution
Removed the direct
pull_requesttrigger fromoperator-ci.yml. The workflow now only runs via:workflow_call(fromrun-on-pr.ymlandrun-on-main.yml)workflow_dispatch(for manual triggering)This ensures the operator CI runs exactly once per PR while maintaining coverage for all changes.
🤖 Generated with Claude Code