Add backport workflow #9172
Merged
Add backport workflow #9172
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
joshcooper
commented
Nov 28, 2023
If a label starting with "backport <branch>" is applied to an already merged PR
then create a new PR against <branch> where the commits are cherry picked from
the original PR using the '-x' flag to include the original git ref.
Note the pull_request_target trigger comes with a security warning[1]:
you should make sure that you do not check out, build, or run untrusted
code from the pull request with this event.
To guard against this we only run if the label is applied to an already merged
PR and not a closed, but unmerged PR.
[1] https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#pull_request_target
tvpartytonight
approved these changes
Dec 2, 2023
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.
If a label starting with "backport " is applied to an already merged PR then create a new PR against where the commits are cherry picked from the original PR using the '-x' flag to include the original git ref.
Note the pull_request_target trigger comes with a security warning[1]:
To guard against this we only run if the label is applied to an already merged PR and not a closed, but unmerged PR.
[1] https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#pull_request_target