chore: rename default branch master -> main (in-repo references) - #129
Merged
Conversation
GitHub's branch rename does not touch in-repo references. Swap every functional and cosmetic mention of the default branch name: - workflows: run_test/run_cypress/run_test_windows push filter '!master' -> '!main'; run_test & build_and_deploy release-type `case` arm master) -> main); jekyll-gh-pages `branches` -> ["main"]; build_and_deploy comment. - docs: user_guide graphview .md/.en.md `blob/master/` design-doc link -> `blob/main/`; README, TEST_GUIDE.md, documentMD/design/testing.md, test/README.md prose. gitOperator.js:51 regex already matches (master|main); no source change. Merge alongside / just after the GitHub Settings branch rename. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017xw6DdyQhrdTZMjYbKvFZi
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
1 participant
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.
Purpose
In-repo companion to renaming the default branch
master→mainin repoSettings. GitHub's rename retargets PRs / moves branch protection / adds
redirects but does not edit references to the branch name inside the repo.
Changes (11 files)
Functional — would break on rename:
run_test.yml,run_cypress.yml,run_test_windows.yml: push filter- '!master'→- '!main'(keeps per-push UT/E2E off the default branch).run_test.yml+build_and_deploy.yml: release-typecasearmmaster) TYPE=release→main)(otherwise mainline builds fall through tobetaand lose:latest+ the "Latest" release).jekyll-gh-pages.yml:branches: ["master"]→["main"](GitHub Pagesdoc-site deploy trigger).
documentMD/user_guide/.../1_graphview.md+.en.md: design-doc link/blob/master/→/blob/main/.Cosmetic: comments in
build_and_deploy.yml; prose inREADME.md,TEST_GUIDE.md,documentMD/design/testing.md,test/README.md.server/test/app/core/gitOperator.js:51regex already matches(master|main)— no source change needed.
Merge sequence
master→mainin Settings → General → Default branch (GitHubauto-retargets this PR's base to
main).mainimmediately (keep a short push/release freezeacross steps 2–3).
Out of scope:
maintenance2023/maintenance2026keep their names; theirworkflow copies still carry a now-dead
master)arm — harmless, tidy later.🤖 Generated with Claude Code