CI: prevent duplicate triggering of build workflow #891
Conversation
This file contains 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
Builds are triggered on pushes to the repo and when a PR is updated. If a PR from a branch in the same repo is pushed to, both triggers activate, starting each job twice. This change guards against this case.
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.
Builds are triggered on pushes to the repo and when a PR is updated. If a PR from a branch in the same repo is pushed to, both triggers activate, starting each job twice.
This change guards against this case by limiting push-builds to the master branch, at the cost of not triggering CI builds for pushes to other branches in the repo, if there is no PR for them.