Disable PR testing for 202311 branch#19419
Merged
StormLiangMS merged 1 commit intosonic-net:202311from Jul 7, 2025
Merged
Conversation
Support for release 202311 has ended. This PR disables PR pipeline triggers for the 202311 branch. Signed-off-by: Xin Wang <[email protected]>
Collaborator
|
/azp run |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
9 tasks
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
3 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.
Description of PR
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
Support for release 202311 has ended. This PR disables PR pipeline triggers for the 202311 branch.
How did you do it?
Set PR trigger to "none" in pipeline yaml file.
How did you verify/test it?
Verify that PR testing is not triggered for this PR.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation