Fix trigger condition for the cherry-pick workflow#8513
Closed
wangxin wants to merge 1 commit intosonic-net:masterfrom
Closed
Fix trigger condition for the cherry-pick workflow#8513wangxin wants to merge 1 commit intosonic-net:masterfrom
wangxin wants to merge 1 commit intosonic-net:masterfrom
Conversation
PR sonic-net#8511 updated the cherry-pick workflow to use lable "Request for 20xx branch". However, the workflow condition was not updated accordingly. The workflow actions are still skipped when labels like "Request for 20xx branch" is set. This change updated the trigger condition in the workflow yaml to match labels start with "Request for 20". Signed-off-by: Xin Wang <[email protected]>
Collaborator
Author
|
Before auto cherry-pick a PR, it is better idea to have approval procedure. Let's follow the same practice of sonic-buildimage repo. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 of PR
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
PR #8511 updated the cherry-pick workflow to use lable "Request for 20xx branch". However, the workflow condition was not updated accordingly. The workflow actions are still skipped when labels like "Request for 20xx branch" is set.
How did you do it?
This change updated the trigger condition in the workflow yaml to match labels start with "Request for 20".
How did you verify/test it?
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation