Add workflow to auto-open PRs to v10 branch #4755
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
|
Will this leave a ton of v10/xxxx branches ? |
|
Is there an option to delete the branch when merging if it's in the same repo? I know there's a setting to do that automatically but I don't remember if it's an option manually. We can always add another workflow to delete them if it's a problem. |
|
I know on my repos, I usually just turn that setting on, we can always restore those branches after the fact when needed and it does not do it to protected branches. |
bdukes
force-pushed
the
release-10-workflow
branch
from
629dc81
to
a9be564
Compare
valadas
approved these changes
Dec 1, 2021
|
This is a release management task, as per our policy, we are self-approving it. |
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
This GitHub Actions workflow should open a PR to the
release/10.0.0branch whenever any PR is merged into thedevelopbranch.Considerations
The
release/10.0.0branch should be created before this is merged.I'm not sure if there's a good way to test this without truly enabling it.
This copies the labels from the original PR. Do we want that, or do we want these v10 merges to always be labelled Type: Maintenance?