[action] Keep 'request for xxx branch' label when finished auto-cherry-pick #13107
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
liushilongbuaa
added
Request for 202012 Branch
Request for 202106 Branch
Request for 202111 Branch
yxieca
approved these changes
Dec 20, 2022
mssonicbld
pushed a commit
to mssonicbld/sonic-buildimage
that referenced
this pull request
Jan 5, 2023
…y-pick. (sonic-net#13107) Why I did it To keep 'Request for xxx branch' label when finished auto-cherry-pick. How I did it Change logic in post cherry pick action. How to verify it
|
Cherry-pick PR to 202205: #13272 |
mssonicbld
pushed a commit
that referenced
this pull request
Jan 5, 2023
…y-pick. (#13107) Why I did it To keep 'Request for xxx branch' label when finished auto-cherry-pick. How I did it Change logic in post cherry pick action. How to verify it
mssonicbld
added
Included in 202205 Branch
and removed
Approved for 202205 Branch
Created PR to 202205 Branch
labels
mssonicbld
pushed a commit
to mssonicbld/sonic-buildimage
that referenced
this pull request
Jan 8, 2023
…y-pick. (sonic-net#13107) Why I did it To keep 'Request for xxx branch' label when finished auto-cherry-pick. How I did it Change logic in post cherry pick action. How to verify it
|
Cherry-pick PR to 202211: #13300 |
mssonicbld
pushed a commit
that referenced
this pull request
Jan 8, 2023
…y-pick. (#13107) Why I did it To keep 'Request for xxx branch' label when finished auto-cherry-pick. How I did it Change logic in post cherry pick action. How to verify it
mssonicbld
added
Included in 202211 Branch
and removed
Approved for 202211 Branch
Created PR to 202211 Branch
labels
qiluo-msft
pushed a commit
that referenced
this pull request
Jan 12, 2023
…y-pick. (#13107) Why I did it To keep 'Request for xxx branch' label when finished auto-cherry-pick. How I did it Change logic in post cherry pick action. How to verify it
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.
Why I did it
To keep 'Request for xxx branch' label when finished auto-cherry-pick.
How I did it
Change logic in post cherry pick action.
How to verify it
Which release branch to backport (provide reason below if selected)
Description for the changelog
Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU.
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)