-
Notifications
You must be signed in to change notification settings - Fork 255
ci: Future proof GitHub merge queue branch trigger for release/* branches #3807
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Co-authored-by: jpayne3506 <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We are limiting the changes to only .pipelines/pipeline.yaml
Co-authored-by: jpayne3506 <[email protected]>
Done. I've reverted the NPM pipeline changes and limited the scope to only |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lets change release/v* to release/ in order to capture more scenarios
…d of release/v* Co-authored-by: jpayne3506 <[email protected]>
Updated the trigger patterns from |
Co-authored-by: jpayne3506 <[email protected]>
Logic:
|
/azp run Azure Container Networking PR |
Azure Pipelines successfully started running 1 pipeline(s). |
…ches (Azure#3807) * Initial plan * feat: update pipeline triggers to be specific to release/v* branches Co-authored-by: jpayne3506 <[email protected]> * chore: revert NPM pipeline changes to limit scope to main pipeline only Co-authored-by: jpayne3506 <[email protected]> * feat: update release triggers to use broader pattern release/* instead of release/v* Co-authored-by: jpayne3506 <[email protected]> * fix: correct GitHub merge queue trigger pattern for release branches Co-authored-by: jpayne3506 <[email protected]> --------- Co-authored-by: copilot-swe-agent[bot] <[email protected]> Co-authored-by: jpayne3506 <[email protected]>
This PR makes the Azure Pipeline trigger future proof when creating new
release/v*
feature branches by updating trigger patterns to be more specific and targeted.Changes Made
🔧 Pipeline Trigger Updates
Main Pipeline (
.pipelines/pipeline.yaml
):release/*
torelease/v*
for more precise matchinggh-readonly-queue/release/v*/*
for release branch merge queue supportNPM Pipelines:
.pipelines/npm/npm-scale-test.yaml
PR trigger fromrelease/*
torelease/v*
.pipelines/npm/npm-conformance-tests.yaml
PR trigger fromrelease/*
torelease/v*
Technical Details
The new
release/v*
pattern will:release/v1.0
,release/v2.0.1
,release/v1.0-alpha
release/feature-branch
,release/hotfix
Benefits
release/v*
branches automatically trigger appropriate pipelinesValidation
All changes have been validated for:
Fixes #3806.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.