Skip to content

Pipelines: Removes master from CI trigger filters#5813

Open
NaluTripician wants to merge 3 commits intomainfrom
users/ntripician/rename-default-branch-ci-cleanup
Open

Pipelines: Removes master from CI trigger filters#5813
NaluTripician wants to merge 3 commits intomainfrom
users/ntripician/rename-default-branch-ci-cleanup

Conversation

@NaluTripician
Copy link
Copy Markdown
Contributor

Removes master from trigger:/schedules: branch filters in every actively-triggered Azure Pipelines YAML now that main is verified to be firing CI correctly. Final cleanup of the master→main rename.

See Software Freedom Conservancy: Renaming the default git branch.

This is PR C of 3:

⚠️ Do NOT merge until PR B has been merged, the GitHub branch rename has occurred, and CI is verified firing on main. Branched off PR B (users/ntripician/rename-default-branch-ci-add-main) so the diff cleanly shows only the master removal — when PR B merges first, this branch will rebase cleanly onto main.

Files changed

File Change
azure-pipelines.yml drop - master
azure-pipelines-functional.yml drop - master
azure-pipelines-cron.yml drop - master
azure-pipelines-nightly.yml drop - master
azure-pipelines-rolling.yml drop - master (×2)

5 files, -6 lines.

Pre-merge checklist

NaluTripician and others added 2 commits April 25, 2026 11:32
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>
Drops 'master' from trigger/schedule branch filters now that 'main' is
verified to be triggering CI correctly. This is the cleanup PR following
the GitHub default-branch rename.

Files:
- azure-pipelines.yml
- azure-pipelines-functional.yml
- azure-pipelines-cron.yml
- azure-pipelines-nightly.yml
- azure-pipelines-rolling.yml

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines:
1 pipeline(s) were filtered out due to trigger conditions.

Base automatically changed from users/ntripician/rename-default-branch-ci-add-main to master April 30, 2026 17:57
…me-default-branch-ci-cleanup

# Conflicts:
#	azure-pipelines-cron.yml
#	azure-pipelines-functional.yml
#	azure-pipelines-nightly.yml
#	azure-pipelines-rolling.yml
#	azure-pipelines.yml
@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines:
Successfully started running 1 pipeline(s).

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines:
Successfully started running 1 pipeline(s).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant