Point branch references at main instead of master - #598
Merged
Conversation
The default branch was renamed master -> main on 2026-05-16, but the in-repo references to it were never updated. Consequences: - The Buildkite badge requested ?branch=master, so it rendered the last build that branch ever saw -- a stale failure -- while main was green. Same for the Codecov badge. - The CI and Documentation workflows trigger on push to master, so neither has run on a push to the default branch since the rename. Only pull_request and scheduled runs were still firing. - Documenter deployed dev docs from a devbranch that no longer exists.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #598 +/- ##
=======================================
Coverage 79.11% 79.11%
=======================================
Files 50 50
Lines 3376 3376
=======================================
Hits 2671 2671
Misses 705 705 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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.
The default branch was renamed
master->mainbetween 2026-05-16 02:26 UTC and 2026-05-17 02:30 UTC, but the in-repo references to it were never updated. Four of them are still stale.Buildkite badge (
README.md)The badge requested
?branch=master, so Buildkite rendered the last build that branch ever saw — a stale failure — even thoughmainis green:…svg?branch=master(before)failing…svg?branch=main(after)passingCodecov badge (
README.md)Same failure mode: pinned to
/branch/master/, which no longer receives coverage uploads.CI and Documentation workflows
.github/workflows/{ci,docs}.ymltrigger onpush: branches: [master]. Since that branch no longer exists, neither workflow has run on a push to the default branch since the rename — onlypull_requestand scheduled runs were still firing.Note that this fix only takes effect once merged, since GitHub reads
on:from the branch being pushed.Documenter
docs/make.jlhaddevbranch = "master", so thedevdocs were not being deployed frommain.For reference,
.github/workflows/Format.ymlalso containsmaster, but that is part of an upstream Runic.jl raw URL and is intentionally left alone.