[CI/CD] Refactor backports flow so that it can determine automatically where to do a backport based on labels #7976
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR changes the command-backport.yml flow so that the branch names are not hardcoded in the pipeline file but will be parsed from the labels.
The idea is that there are going to be a label representing each stable branch:
If the backport is needed to any of those branches or to all of them, the corresponding label can be set on the PR and the branch name will be parsed from it.
The labels need to be created in the repo and adjusted as soon as there is a new release appears or an old one disappears.