Repository navigation
ci: prevent duplicate workflow runs - #136
Merged
Merged
Conversation
vmarkop
approved these changes
Oct 13, 2026
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
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.
Before
Our workflows ran on both
push(to any branch) andpull_request. So every commit pushed to a PR branch started each workflow twice: once because a branch was pushed, and once because a PR was updated. Both runs checked essentially the same code.Also, if you pushed several commits in a row, every one of them ran to completion, even though only the latest one mattered.
Now
pull_request, pluspushtomasteronly (so merged code still gets checked).masterstill gets a full run.What changes in practice
Pushing a branch without a PR no longer starts any CI. If you want CI feedback early, open a draft PR.