Skip to content

chore: replace stale 'master' branch refs with 'main' (post-rename cleanup)#39

Merged
yakuphanycl merged 1 commit into
mainfrom
chore/cleanup-master-refs
Apr 26, 2026
Merged

chore: replace stale 'master' branch refs with 'main' (post-rename cleanup)#39
yakuphanycl merged 1 commit into
mainfrom
chore/cleanup-master-refs

Conversation

@yakuphanycl
Copy link
Copy Markdown
Contributor

Summary

Post-rename cleanup. The default branch was renamed mastermain 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.

What changes

8 occurrences across 5 files, all pure ref-cleanup:

File Occurrences Change
.github/workflows/ci.yml 2 branches: [main, master][main] (master no longer receives pushes; defensive dual-listing is dead code)
.github/workflows/codeql.yml 2 Same as ci.yml
pyproject.toml 1 Changelog URL blob/master/CHANGELOG.mdmain (PyPI metadata)
README.md 3 CI badge + CodeQL badge ?branch=master + License link blob/master/ → all main
SECURITY.md 1 "latest release on master" → "on main"

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 mastermain rename 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 --stat shows 5 files / 9 insertions / 9 deletions (line-for-line replacement)
  • grep -rn "master" .github/ pyproject.toml README.md SECURITY.md returns empty (verified pre-commit)
  • CI runs cleanly on this branch (will verify post-push)
  • CodeQL runs cleanly on this branch (will verify post-push)
  • After merge: weekly Monday CodeQL schedule continues to fire (cron unchanged, only branch trigger changed)

🤖 Generated with Claude Code

…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>
@yakuphanycl yakuphanycl merged commit 122be51 into main Apr 26, 2026
11 checks passed
@yakuphanycl yakuphanycl deleted the chore/cleanup-master-refs branch April 26, 2026 10:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant