Docs: Refactors master branch references to main#5811
Merged
NaluTripician merged 1 commit intomasterfrom Apr 29, 2026
Merged
Conversation
Renames git-branch references from master to main in documentation, agent playbooks, helper scripts, and YAML template prose ahead of the GitHub default-branch rename. See https://sfconservancy.org/news/2020/jun/23/gitbranchname/. Scope: - README.md, CONTRIBUTING.md, changelog.md (link only), .gitignore - docs/*.md (excluding Cosmos master/multi-master terminology) - .github/copilot-instructions.md and .github/agents/*.md - tools/msdata-direct-sync-helper.ps1 - templates/build-preview.yml, templates/static-tools-encryption*.yml prose Out of scope (intentionally untouched): - Pipeline trigger filters in azure-pipelines*.yml (handled in a follow-up PR) - Cosmos product terminology (multi-master, single-master, master key, MasterKey) - Historical changelog PR titles Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
Azure Pipelines: Successfully started running 1 pipeline(s). |
This was referenced Apr 25, 2026
|
Azure Pipelines: Successfully started running 1 pipeline(s). |
kushagraThapar
approved these changes
Apr 28, 2026
Member
kushagraThapar
left a comment
There was a problem hiding this comment.
LGTM, thanks @NaluTripician
tvaron3
approved these changes
Apr 29, 2026
NaluTripician
added a commit
that referenced
this pull request
Apr 30, 2026
Adds `main` alongside `master` to the `trigger:`/`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](https://sfconservancy.org/news/2020/jun/23/gitbranchname/). This is **PR B of 3**: - PR A (#5811) — docs / agents / scripts - **PR B (this PR)** — adds `main` to CI trigger filters, transitional, dual-branch - PR C — drops `master` from CI trigger filters once `main` is verified⚠️ **Do NOT merge until Monday's coordinated cutover.** This PR must be merged immediately *before* the GitHub branch rename so CI continues firing on both `master` (until rename) and `main` (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 | File | Change | | --- | --- | | `azure-pipelines.yml` | `pr.branches.include` adds `- main` | | `azure-pipelines-functional.yml` | `pr.branches.include` adds `- main` | | `azure-pipelines-cron.yml` | `schedules[*].branches.include` adds `- main` | | `azure-pipelines-nightly.yml` | `schedules[*].branches.include` adds `- main` | | `azure-pipelines-rolling.yml` | Both `schedules[*].branches.include` blocks add `- main` | 5 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. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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
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.
Renames git-branch references from
mastertomainin documentation, agent playbooks, helper scripts, and YAML template prose, ahead of the planned GitHub default-branch rename.See Software Freedom Conservancy: Renaming the default git branch for context.
This is PR A of 3:
maintotrigger:filters in azure-pipelines*.yml (alongsidemaster, transitional) — to be merged immediately before the GitHub branch renamemasterfromtrigger:filters oncemainis verified in CIWhat changed
README.md,CONTRIBUTING.md,changelog.md(link-only),.gitignoredocs/builds-and-pipelines.md,docs/sync_up_msdata_direct.md,docs/caches.md,docs/Cross Region Request Hedging.md,docs/observability.md,docs/LocalQuorum.md.github/copilot-instructions.md,.github/agents/release-copilot-agent.agent.md,.github/agents/msdata-direct-sync-agent.agent.md,.github/agents/issue-fix-agent.agent.mdtools/msdata-direct-sync-helper.ps1templates/build-preview.yml,templates/static-tools-encryption.yml,templates/static-tools-encryption-custom.yml(display names + comments only — no behavior change)Intentionally NOT changed
trigger:filters inazure-pipelines*.yml— handled in PR B / PR C.multi-master,single-master,master key,MasterKey,multimaster,master-key. These are unrelated to the git branch.docs/PerPartitionAutomaticFailoverDesign.mdanddocs/LocalQuorum.mdwrite-account terminology.Stats
18 files changed, 153 insertions(+), 153 deletions(-).