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.
Context
Backporting PRs to previous branch is pretty tedious. You have to:
[<branch>] <title of PR to backport>
Summary
This PR is just an idea of a workflow that does all of this for us. The idea is you can just click on the
Backport PR
GHA workflow. Here's a screenshot of the workflow where the branch selected would be the target, the user must specify which PR number to backport and whether or not to cherry-pick the commit (the idea here is that we would still gain from everything even if we create an empty commit that can be edited).Here's an example result from just running the script: #508.
Here's an example result from running in GHA: tomleb#11. Pretty much the same thing.
Note: I'd like some input from the team to know whether that's something they'd be interested in. I can totally run this script locally but if the whole team can benefit from it then why not.
Note: This could also be in the form of a github bot that reacts to comments, though that involves more work. (eg: Image just having to write
/backport release/v0.4
in a merged PR.Note: The script only supports squash commits. Now that squashed commits are enforced, this shouldn't be an issue in the future.
Possible improvements