chore: replace stale 'master' branch refs with 'main' (post-rename cleanup)#39
Merged
Conversation
…eanup) The default branch was renamed master → main on 2026-04-26 via atomic gh api .../branches/master/rename. GitHub auto-redirect kept all old 'master' references working transparently, but the hardcoded refs should be replaced for clarity and to avoid surprise on future tooling that doesn't follow redirects. Replaces 8 occurrences across 5 files: 1. .github/workflows/ci.yml × 2 — `branches: [main, master]` → `[main]` (master no longer receives pushes; the defensive dual-listing is now dead code) 2. .github/workflows/codeql.yml × 2 — same as ci.yml 3. pyproject.toml — Changelog URL `blob/master/CHANGELOG.md` → `main` (PyPI metadata; auto-redirect works but cleaner to point at the live ref) 4. README.md × 3 — CI badge, CodeQL badge, License link all `?branch=master` / `blob/master/` → `main` (badges currently render fine via redirect but the badge URL parameter is the canonical source) 5. SECURITY.md — "latest release on `master`" → "on `main`" No code or behaviour changes. Pure ref-cleanup post the master→main rename. Internal memory entry: fix_instinct_default_branch_rename.md documented this cleanup as deferred Tier 3 polish; this PR closes it. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.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.
Summary
Post-rename cleanup. The default branch was renamed
master→mainon 2026-04-26 via atomicgh api .../branches/master/rename. GitHub auto-redirect kept all oldmasterreferences working transparently, but the hardcoded refs should be replaced for clarity and to avoid surprise on future tooling that doesn't follow redirects.What changes
8 occurrences across 5 files, all pure ref-cleanup:
.github/workflows/ci.ymlbranches: [main, master]→[main](master no longer receives pushes; defensive dual-listing is dead code).github/workflows/codeql.ymlpyproject.tomlblob/master/CHANGELOG.md→main(PyPI metadata)README.md?branch=master+ License linkblob/master/→ allmainSECURITY.mdmaster" → "onmain"What does NOT change
No code, no behaviour, no test surface. Workflows continue to trigger on the same branch (just now spelled correctly). PyPI Changelog link continues to resolve (auto-redirect already worked; this just bypasses the redirect). Badges continue to render (canonical URL parameter updated).
Why now
Surfaced as deferred Tier 3 polish in the 2026-04-26 cross-repo health check after the
master→mainrename shipped. Auto-redirect masking these refs means there was no production urgency, but they're a small papercut for readers and an obvious gotcha for the next agent doing tooling work on this repo.Test plan
git diff --statshows 5 files / 9 insertions / 9 deletions (line-for-line replacement)grep -rn "master" .github/ pyproject.toml README.md SECURITY.mdreturns empty (verified pre-commit)🤖 Generated with Claude Code