[infra] Introduce automated cherry-picking workflow #15262
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
michelengelen
added
the
scope: infra
michelengelen
requested review from
flaviendelangle,
LukasTy,
JCQuintas,
MBilalShafi and
cherniavskii
|
Deploy preview: https://deploy-preview-15262--material-ui-x.netlify.app/ |
JCQuintas
approved these changes
Nov 5, 2024
michelengelen
added a commit
to michelengelen/mui-x
that referenced
this pull request
Nov 5, 2024
This reverts commit 03b17aa.
michelengelen
added a commit
that referenced
this pull request
Nov 5, 2024
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.
Changes the workflow to use the automated cherry=pick PR creation process designed in mui/mui-public#217
The new workflow can now automatically create PRs for several types of base-target combinations:
mastertov*.xOn your PR add the
needs-cherry-picklabel and one or more target-labels (e.g.v7.x,v6.x). The workflow will create a cherry-pick PR to the highest version branch first (in this casev7.x) and adds theneeds cherry-picklabel and the remaining target-labels (in this casev6.x) if needed. This makes the workflow "de-facto recursive".v*.xtov*.xFor any PR from a version branch that has the
needs-cherry-picklabel and target-labels applied the process from option 1 will apply.v*.xtomasterFor any PR from a version branch that has the
needs-cherry-picklabel applied this workflow will create a cherry-pick PR targetingmasterautomatically.As a follow-up to mui/mui-public#217 I will also add a new workflow later this week to apply mui/mui-public#220