[action] [PR:20382] Ensure pre-test is the first item in conditional mark check#20581
Merged
mssonicbld merged 1 commit intosonic-net:202505from Sep 9, 2025
Merged
Conversation
…t#20382) Ensure pre-test is first item in conditional mark check, because pre-test runs before everything else, and it makes the most sense at the top of the file. Also this change goes with sonic-net#20326 This change will allow that PR to pass its PR checks.
7 tasks
Collaborator
Author
|
Original PR: #20382 |
Collaborator
Author
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
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
2 participants
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.
Summary:
Ensure pre-test is first item in conditional mark check, because pre-test runs before everything else, and it makes the most sense at the top of the file.
Also this change goes with #20326
This change will allow that PR to pass its PR checks.
Type of change
Back port request
Approach
What is the motivation for this PR?
To allow #20326 to pass the PR checks
How did you verify/test it?
Running it manually on PR 20326
Any platform specific information?
No
Supported testbed topology if it's a new test case?
N/A