CI: Limit build-on-push to master branch only #335
Merged
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
All good, marking this not-a-draft |
Dependabot pushes to main repository and ends up triggering two builds every time (one for PR, one for push): limit the rule for build-on-push to apply to master branch only. If release branches are used later on they should be added to list here.
jku
changed the title
jku
force-pushed
the
build-on-push-to-develop-only
branch
from
07ab2a6
to
7de4893
Compare
joshuagl
approved these changes
Feb 17, 2021
Merged
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.
Dependabot pushes to main repository and ends up triggering two builds
every time (one for PR, one for push): limit the rule for build-on-push
to apply to master branch only.
If release branches are used later on they should be added to list here.
This was already done in TUF: we can wait for dependabot to react to the daily cryptography release (sigh) to see if the TUF version works correctly before merging this...