Ensure the cherry pick operation only executes against trunk
#47312
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.
Submission Review Guidelines:
Changes proposed in this Pull Request:
If a PR is merged with a milestone (or a milestone is added to a PR after it's merged) that targets a branch other than trunk, we shouldn't run the cherry-pick workflow.
Closes #38896
How to test the changes in this Pull Request:
Using the WooCommerce Testing Instructions Guide, include your detailed testing instructions:
Disable unnecessary workflows in your Fork to save bandwidth (you only need this workflow to be operational)
Create some milestones for testing purposes e.g.
9.1.0
,9.0.0
,8.9.0
,8.8.0
Create and merge a PR in your Fork targeting trunk for testing purposes. If you have one already, you can use it.
This PR will likely be assigned a valid Milestone e.g. 9.0.0 if the appropriate workflow is enabled on your fork.
Attempt to 'cherry pick' the PR created in step 6 into a release branch by assigning it another milestone e.g. 8.9.0
Validate that the cherry pick operation kicks off and attempts to perform the appropriate cherry-picking by progressing to the Prep inputs task
Create and merge a PR in your Fork targeting a release branch (such as release/8.9) for testing purposes. If you have one already, you can use it.
Attempt to 'cherry pick' this PR into a release branch by assigning it another milestone e.g.
8.9.0
Validate that the cherry pick operation does not kick off and does not attempt to perform the appropriate cherry-picking and does not progress to the Prep inputs task
Changelog entry
Significance
Type
Message
Comment