Request: rename `master` → `main` on cloudfoundry/stratos

[norman-abramovitz]

Request

Please rename the master branch of cloudfoundry/stratos to main (GitHub branch rename, preserves history/refs). This requires an org admin because master is protected, and renaming a protected branch needs admin access — repo maintainers (push) get a 403 (verified).

Context — already reviewed and approved

• Plan of record: Establish main as the release branch (rename master → main) stratos#5507 — main becomes the release branch (rc + stable); develop stays the dev integration/default branch (unchanged).
• Branch protection for main is already pre-staged in orgs/branchprotection.yml via Add explicit branch protection for cloudfoundry/stratos (develop + main) #1537 (approved by @Gerg, @beyhan, @rkoster; merged 2026-06-30). allow_disabled_policies: true tolerates the gap until the rename lands — the config comment cites stratos#5507 for exactly this step.

Low risk

• master is dormant: last commit 2026-02-25, ~1404 commits behind develop.
• Zero open PRs target master.
• GitHub auto-retargets PRs and redirects web URLs on rename.
• A stratos PR swapping the in-repo master refs (workflow triggers, release-sync pipeline, chart icon raw URL, docs) is ready and will land alongside.

Owner

App Runtime Interfaces WG, Stratos Console for Cloud Foundry area.

[nabramovitz]

The in-repo ref-swap PR is now staged as a draft: cloudfoundry/stratos#5538. It will be marked ready and merged immediately after the rename executes.

[beyhan]

Hi @norman-abramovitz,

I renamed the master branch to https://github.com/cloudfoundry/stratos/tree/main.

[norman-abramovitz]

Thanks @beyhan! The rename is confirmed on our side — main is live and the old master refs resolve via the redirect.

The in-repo follow-up landed in cloudfoundry/stratos#5538, which retargets all workflow, docs, and tooling references from master to main. That completes everything requested here, so closing.