-
Couldn't load subscription status.
- Fork 89
Add 0.18 forward-porting into 0.19 #1382
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
base: series/0.18
Are you sure you want to change the base?
Conversation
|
besides the fact that this actually sets up fore-port (not back-port), do you want to revisit this in order to automate the process a little more ? |
|
yes. PR is called "backport action" because that's how Mergify calls it in the config ;) I may try revisiting it now that you've sniped me |
| conditions: | ||
| - author=scala-steward | ||
| - status-success="build-success-checkpoint" | ||
| - check-success="build-success-checkpoint" |
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.
status-success apparently isn't a thing - https://docs.mergify.com/configuration/conditions/
|
@Baccata that should do it. Tested in a repo of mine (without the required status check, but I trust that'll work properly) - kubukoz/demos#8 |
| conditions: | ||
| - label="forwardport-0.19" |
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.
question: do we need a label? I'd say we should do it automatically (that way it'll be much less trouble with things like Steward), or with opt-out via a "do not port" label.
PR Checklist (not all items are relevant to all PRs)