ensure CNAME is 'occupied'#102
Merged
Merged
Conversation
IgorTatarnikov
approved these changes
Jun 10, 2026
IgorTatarnikov
left a comment
IgorTatarnikov
left a comment
Member
There was a problem hiding this comment.
This looks good to me! Let's try merging it and re-rendering the website to see if it works.
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.
Description
What is this PR
Why is this PR needed?
Ensure the dashboard website claims the CNAME throughout.
How has this PR been tested?
quarto renderlocally copies the CNAME into the local build folder, which my AI assistant suggests is key for "claiming" it.cnameas an optionI don't really know how much of this is overkill (setting the
cnamein the workflow might be enough), but it won't hurt.