mergify: support for some backport aliases

[v1v]

this should help with backporting to the current active branches

without knowing the active minor but using the major one

Release notes

What does this PR do?

Maybe this is solved already, but is there a way we can get an automatically kept up to date “backport-active-minors” label that auto backports to the set of minor releases that are still supported? I’d want this in Beats, Elastic Agent, and Fleet Server if it already exists. I’ve noticed an increase in forgotten backports because there are more releases to keep track of. If we can abstract this it’d make life easier, I think Kibana does something like this

We, observability robots team, are responsible for keeping those aliases in sync - we are working on the automation for that.

Why is it important/What is the impact to the user?

Enable backport-active-all, backport-active-8 and backport-active-9 GitHub labels in Mergify to backport to a set of active branches in addition to the existing automation with the backport-<major>.<minor> labels. This can help with the current 6 active branches, which we have today.

Therefore, if a PR takes longer to be merged, these aliases can help avoid the burden of updating the backport-[major].[minor] labels.

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files (and/or docker env variables)
• I have added tests that prove my fix is effective or that my feature works

Author's Checklist

• [ ]

How to test this PR locally

Related issues

• Similarly solved in other projects:
  • mergify: support backport-active-8, backport-active-9 and backport-active-all  fleet-server#4404

Use cases

Screenshots

Logs

[mergify]

This pull request does not have a backport label. Could you fix it @v1v? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit.
• backport-8.x is the label to automatically backport to the 8.x branch.

[mergify]

backport-8.x has been added to help with the transition to the new branch 8.x.
If you don't need it please use backport-skip label.

[mergify]

This pull request does not have a backport label. Could you fix it @v1v? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit.
• backport-8.x is the label to automatically backport to the 8.x branch.

[mergify]

backport-8.x has been added to help with the transition to the new branch 8.x.
If you don't need it please use backport-skip label.

[mergify]

This pull request is now in conflicts. Could you fix it @v1v? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b feature/support-active-all-aliases-mergify upstream/feature/support-active-all-aliases-mergify
git merge upstream/main
git push upstream feature/support-active-all-aliases-mergify

[mashhurs]

This is awesome! Thank you so much.