-
-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Something is wrong with our dns #356
Comments
The CNAME does not seem to have helped |
When we're having an outage, there is no CNAME file on the gh-pages branch, and updating the field adds one |
Just came across this issue from Mastodon, and thought I could help! I guess that Instead, you should create/generate a CNAME file in the output directory (
Alternatively, there is a
You can also check the other configuration options of the action, such as excluding specific files to prevent the action from deleting CNAME. Hope this helps! |
Thanks for stopping by @ysfchn -- I tried that and just had my first clean deploy! Thanks so much! |
Glad I was able to help! 😄 |
Every time we deploy, I have to re-set the custom domains on settings > pages, which it doesn't seem like I should have to do. Maybe we need a CNAME file?
The text was updated successfully, but these errors were encountered: