-
Notifications
You must be signed in to change notification settings - Fork 19
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
Backport via label did not trigger #50
Comments
Hum, I think the issue is arround here:
I can't promise I'll fix this soon, but I can give you access to this repo and heroku if you want to try to fix it yourself. |
For now hardcode both master and main.
Oh, actually the labels are taken care of a bit higher, so it might just be "master"/"main" I've tried to push a workaround. |
Thanks! I'll keep an eye on it and report back. We don't backport every day. |
Seeing MeeseeksBox/test1#84 that should work now. |
Yay, it indeed works now. Thank you so much for the quick fix! |
https://meeseeksbox.github.io/ mentioned that it is possible to trigger backport via label as long as description has the directive. Over at https://github.com/astropy/astropy/labels , we have a
backport-v4.3.x
label with the description as required. But when applied to, say astropy/astropy#11971, it did not trigger backport bot to open a backport PR on merge. What did we do wrong? Hope you can advise. Thanks!The text was updated successfully, but these errors were encountered: