[ci] enable PR checker trigger for release branches#382
Merged
yxieca merged 1 commit intoJun 16, 2026
Conversation
Signed-off-by: Yijing Yan <yijingyan@microsoft.com>
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
yxieca
approved these changes
Jun 16, 2026
yxieca
left a comment
yxieca
left a comment
Contributor
There was a problem hiding this comment.
Correct and complete. Adding 202??? to both trigger: and pr: validates release-branch builds and PRs — the 202605 branch exists here, so these were previously unverified.
Checked:
- The
202???glob is right —?matches a single character in Azure DevOps branch filters, so it matches202605,202505, etc., consistent with the rest of sonic-net. - Good that both
trigger:andpr:were updated. - Azure pipeline is green.
One small thing: the PR description says "The Azure Pipelines PR checker for sonic-dash-ha…" — looks like a copy-paste from the sibling PR; this repo is sonic-snmpagent. Worth fixing the body, not blocking.
LGTM.
Collaborator
|
Cherry-pick PR to 202605: #384 |
mssonicbld
added
Included in 202605 Branch
and removed
Created PR to 202605 Branch
labels
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.
Approach
What is the motivation for this PR?
The Azure Pipelines PR checker for sonic-dash-ha only triggered on PRs targeting the master branch. PRs raised against release branches (e.g. 202605) did not run the PR validation pipeline, leaving release-branch changes unverified.
How did you do it?
Added the 202??? branch pattern to the pr.branches.include list so the PR checker also triggers for release branches.