Change backport action to accept target versions for porting via checkboxes and select current issue's version from a list #8236
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…t-to to generate issues
oracle-contributor-agreement
bot
added
the
OCA Verified
tomas-langer
approved these changes
Jan 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
In the current backport GitHub action, the user enters the current version of the issue being ported and automatically ports to all other versions.
This change displays the current version as a choice list (from which the user chooses one) and present check boxes for the versions to port to with the other releases defaulted for porting to.
There is no validity checking in the yaml but the changes to the bash script, as before, make sure to not create another issue targeted to the same version as the original script.
I kept the same defaults--existing issue version is 2.x and default targets are 3.x and 4.x--for compatibility with the original action but we could certainly change that. I think it's probably now a more frequent use case that we port from 4.x to 3 and/or 2.