[ci] run CI on pull requests targeting release/ branches #5527
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
40 tasks
jmoralez
approved these changes
Oct 8, 2022
|
thanks so much for the quick review, @jmoralez ! |
jameslamb
added a commit
that referenced
this pull request
Dec 6, 2022
jameslamb
added a commit
that referenced
this pull request
Dec 6, 2022
|
This pull request has been automatically locked since there has not been any recent activity since it was closed. To start a new related discussion, open a new issue at https://github.com/microsoft/LightGBM/issues including a reference to this. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Based on @guolinke 's suggestion in #5525 (comment), I'd like to try targeting PR #5525 at a branch,
release/v3.3.2, which only contains:masterThat would allow us to try to run all of LightGBM's CI over the potential
v3.3.3release (we'll see if that works!).This PR proposes modifying the configs for GitHub Actions and Azure Devops so that CI jobs will be triggered on all
branchesPRs targeting branches with a name likerelease/*.Once this is merged, I'll update #5525.
Notes for reviews
Documentation for how these configs work:
It isn't necessary to modify the Appveyor config....I believe it just builds for all branches automatically.