Repository navigation
chore: remove the stray root CNAME - #12
Merged
Merged
Conversation
GitHub's Settings -> Pages UI wrote a CNAME at the repo root when the custom domain was first set. It has never been part of the deploy: Pages publishes the Actions artifact, which is dist/, and dist/CNAME comes from public/CNAME. The workflow already asserts that file exists. Two copies of the same setting invites the wrong one being edited later, and they had already drifted apart on trailing newline. public/CNAME is the one that ships, so it is the one that stays. Co-authored-by: Claude <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
2 participants
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.
GitHub's Settings → Pages UI wrote a
CNAMEat the repo root when the custom domain was first set (commitbc22fd9, "Create CNAME"). It has never been part of the deploy.Pages publishes the Actions artifact, which is
dist/, anddist/CNAMEis copied frompublic/CNAME. The deploy workflow already asserts that file survives the build, so the root copy does nothing.Two copies of the same setting invites the wrong one being edited later, and they had already drifted apart — the root file had no trailing newline,
public/CNAMEdoes.public/CNAMEis the one that ships, so it is the one that stays.No changelog entry: nothing a player can see changes.
Checks
npm run test:run— 353 tests across 8 files, all passingnpm run build— cleandist/CNAMEpresent after build, containingjbl.opsvibe.systemsUnrelated: the "Cannot retrieve latest commit" banner
This PR does not fix that, because there is nothing in the repo causing it. Commit
38fdd24resolves fine through the API,git fsckis clean, and the deploy on that commit was green. GitHub is in an active incident (opened 2026-08-17 13:40 UTC) with API Requests, Actions, Webhooks, Issues and Pull Requests all degraded, which is why the banner follows you across browsers and private windows.Generated by Claude Code