-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[core] Add cherry-pick master
to v6
action
#12648
Conversation
Deploy preview: https://deploy-preview-12648--material-ui-x.netlify.app/ |
permissions: | ||
pull-requests: write | ||
contents: write | ||
if: ${{ contains(github.event.pull_request.labels.*.name, 'needs cherry-pick') && contains(github.event.pull_request.labels.*.name, 'v6.x') && github.event.pull_request.merged == true }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we really need the v6.x
label? Seems like 99.9% of PRs will be on master
and when a cherry pick is needed we only add it to v6 anyways, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, technically we don't need it.
I've added the extra check just to have the maximum specificity.
If we agree, then it could just be the same as for next -> master
, simply adding a needs cherry-pick
label would cherry-pick the PR to v6.x
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMHO I would be in favor of that
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removed the extra check. 😉
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Lukas, I was thinking about backporting a couple of PRs, this workflow will help speed it up 🚀
Add an action, which would cherry-pick a PR merged to master into a
v6.x
branch if it would have aneeds cherry-pick
label.Could be useful for bug fixes during the v7 development / v6 maintenance mode.