feature request: use source PR labels to pick branches to backport to

First off: awesome project! Thank you for your work.

I have a feature request, and would love to hear your thoughts. It would be really nice if it were possible to create some feature PR that will later need to be backported. Often you know beforehand where it should be backported to. One could use GitHub labels to mark that all PRs with label backport-v1 should later be backported to the v1 branch. If a label system like that is applied, running backport --pr 123 could read those labels and preselect all the right branches.

Being able to determine ahead of time where we backport to would really improve our workflow. I’m guessing we may not be alone in that.

[sqren]

How about a hybrid (example adapted to my scenario):

I like it 👍

Running backport

For the initial implementation I’ll enable this behaviour when running backport --pr and backport --sha and leave it out for backport --multiple until I have a better idea of how it should behave.

@spalger I think you had a suggestion similar to this a long time ago. Would the hybrid approach work for your use case?

[ronkorving]

@sqren Flippin’ awesome! 😃 I will let you know if anything comes up (although tbh, it may take a while before I get my hands on it).