Add "Dry run" mode to Cherry Picking script #59869
Open
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.
What?
Adds ability to run the Cherry Picking script in a "dry run" mode.
Part of #59399
Why?
It's all too easy to run the Cherry Picking script and have the results propagate to Github. With this flag you can run the script and be sure results will never get propagated.
This is useful when testing locally and for folks getting familiar with the workflow/tooling around releases.
How?
--dry-run
flagTesting Instructions
In a terminal run:
Backport to WP RC/Beta
is used as the "label" to search for and it doesn't accidentally use "--dry-run" as the label if no custom label is provided.Testing Instructions for Keyboard
Screenshots or screencast