ci(test): remove duplicate push trigger on all branches#11
Merged
AperturePlus merged 1 commit intomasterfrom Feb 22, 2026
Merged
ci(test): remove duplicate push trigger on all branches#11AperturePlus merged 1 commit intomasterfrom
AperturePlus merged 1 commit intomasterfrom
Conversation
Why: push on '**' + pull_request on '**' caused two identical CI runs
every time a commit was pushed to a PR branch, wasting runner time.
What: narrow push trigger to master only (post-merge validation);
pull_request continues to cover all PR branches for pre-merge checks.
Test: no logic change, only trigger scope adjusted
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.
Why: push on '' + pull_request on '' caused two identical CI runs
every time a commit was pushed to a PR branch, wasting runner time.
What: narrow push trigger to master only (post-merge validation);
pull_request continues to cover all PR branches for pre-merge checks.
Test: no logic change, only trigger scope adjusted