ci: only trigger on pull_request, remove push trigger to avoid duplicate runs#1323
Merged
Conversation
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
1 participant
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
Remove the
pushtrigger from CI workflow, keeping onlypull_requestandworkflow_dispatch.Rationale
Since this repo does not support direct push to main (all changes go through PRs), the
pushtrigger was redundant — it caused CI to run again after every PR merge. Now CI only runs on PRs, eliminating the duplicate run.The
workflow_dispatchtrigger is retained for manual runs when needed.Changes
pushtrigger fromon:blockpaths-ignoretopull_requesttriggerconcurrencyblock (still useful for cancelling stale runs on the same PR branch)