Update triggers for Integration Checks after default branch change #9666
+5
−71
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
Add main as trigger for Integration Checks Drop develop as trigger for Integration Checks Drop master as trigger for Integration Checks
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.
This PR adds
mainas a push & PR trigger for theIntegration Checksworkflow, replacingdevelopandmaster. Relates to:remotes::install_github#9664Now that the repository's default branch is also the main integration branch, it should be a lot easier to roll out changes to
.github/like:This PR also does what #9564 and #9538 both failed to do—it drops the AppVeyor CI pipeline 🥳 In addition to disabling the relevant webhook, I also had to suspend/remove the AppVeyor app for the
satijalaborganization.