Pipelines: Adds main alongside master in CI trigger filters#5812
Merged
NaluTripician merged 3 commits intomasterfrom Apr 30, 2026
Merged
Pipelines: Adds main alongside master in CI trigger filters#5812NaluTripician merged 3 commits intomasterfrom
NaluTripician merged 3 commits intomasterfrom
Conversation
Adds 'main' to the trigger/schedule branch filters of every actively- triggered Azure Pipelines YAML, alongside the existing 'master' entry. Pipeline branch filters do not follow GitHub's branch-rename redirects, so this transitional change ensures CI keeps firing on both names across the cutover from master to main. Files: - azure-pipelines.yml (PR trigger) - azure-pipelines-functional.yml (PR trigger) - azure-pipelines-cron.yml (schedule) - azure-pipelines-nightly.yml (schedule) - azure-pipelines-rolling.yml (two schedules) Pipelines using 'trigger: none' (official, encryption-official, encryption-custom-official, faultinjection, msdata-direct, msdata-aot, ctl-publishing) configure their branches in the Azure DevOps UI and are updated separately as part of the cutover. A follow-up PR drops 'master' from these filters once 'main' is verified. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
Azure Pipelines: Successfully started running 1 pipeline(s). |
6 tasks
NaluTripician
requested review from
FabianMeiswinkel,
Pilchie,
kirankumarkolli,
kushagraThapar and
sboshra
as code owners
|
Azure Pipelines: Successfully started running 1 pipeline(s). |
NaluTripician
requested review from
jeet1995,
kundadebdatta and
xinlian12
as code owners
|
Azure Pipelines: Successfully started running 1 pipeline(s). |
tvaron3
approved these changes
Apr 29, 2026
|
Azure Pipelines: Successfully started running 1 pipeline(s). |
kushagraThapar
approved these changes
Apr 29, 2026
Member
kushagraThapar
left a comment
kushagraThapar
left a comment
There was a problem hiding this comment.
LGTM, thanks @NaluTripician
NaluTripician
deleted the
users/ntripician/rename-default-branch-ci-add-main
branch
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
4 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.
Adds
mainalongsidemasterto thetrigger:/schedules:branch filters in every actively-triggered Azure Pipelines YAML, ahead of the planned GitHub default-branch rename.See Software Freedom Conservancy: Renaming the default git branch.
This is PR B of 3:
mainto CI trigger filters, transitional, dual-branchmasterfrom CI trigger filters oncemainis verifiedmaster(until rename) andmain(immediately after rename). Pipeline branch filters do not follow GitHub's branch-rename redirects, which is why this transitional dual-include is required.Files changed
azure-pipelines.ymlpr.branches.includeadds- mainazure-pipelines-functional.ymlpr.branches.includeadds- mainazure-pipelines-cron.ymlschedules[*].branches.includeadds- mainazure-pipelines-nightly.ymlschedules[*].branches.includeadds- mainazure-pipelines-rolling.ymlschedules[*].branches.includeblocks add- main5 files, +6 lines.
Out of scope
Pipelines using
trigger: none(azure-pipelines-official.yml,-encryption-official.yml,-encryption-custom-official.yml,-faultinjection.yml,-msdata-direct.yml,-msdata-aot.yml,-ctl-publishing.yml) configure their branches in the Azure DevOps UI and will be updated as part of the cutover, not by a YAML change.