fix(ci): avoid duplicate push and pull_request runs#51
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
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
pushCI runs tomainpull_requeste2ejob-level condition that created skipped duplicate statuses on feature-branch pushesRoot cause
The workflow was triggered by both
pushandpull_requestfor feature branch updates. On commits attached to an open PR, GitHub created both runs. Thee2ejob then skipped in thepushrun because it only allowed PRs ormain, which surfaced as an extra skipped check.Expected effect
PRs should now show only the
pull_requestchecks, while merges tomainstill run the fullpushworkflow.