Rename default branch references from master to main - #568
Open
spoenemann wants to merge 1 commit into
Open
Conversation
The default branch of this repository is renamed to main via the organisation's otterdog configuration. Update the workflow triggers, ADR-0005, and the links into this repository accordingly. The publish workflow now filters maintenance branches with 'maintenance/*', matching the publish environment's branch policy in that configuration. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
spoenemann
force-pushed
the
rename-default-branch
branch
from
September 4, 2026 13:16
7bdc4c6 to
e50fc84
Compare
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.
Summary
Follow-up to the rename of this repository's default branch from
mastertomain, configured in eclipse-sprotty/.eclipsefdn#6. GitHub's rename redirects old URLs and retargets open pull requests, but does not rewrite workflow files, so this PR updates everything in the repository that names the branch:.github/workflows/build.ymlandpublish.ymltrigger onmaininstead ofmaster.publish.ymlfilters maintenance branches withmaintenance/*instead ofmaintenance-*, matching thepublishenvironment's branch policy in the organisation configuration and the convention used across the Sprotty projects.blob/masterlinks in the README and CHANGELOG files point directly tomain(the old links only kept working through the redirect).Links into other repositories (sprotty-theia, sprotty-vscode, sprotty-server, eclipse/.github) are unchanged because those repositories keep their default branch.
Merge order
mastertomain, and this PR is retargeted automatically.maintrigger neither the build nor the publish workflow.Updating local clones
After the rename, run this in every clone that still tracks
master:If you work from a fork, rename the branch there too (repository settings → Branches, or
gh api -X POST repos/<user>/sprotty/branches/master/rename -f new_name=main) and then rungit fetch --prune <fork-remote>.🤖 Generated with Claude Code