-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
storelocator.js.org #8364
storelocator.js.org #8364
Conversation
yoriiis
commented
Jul 10, 2023
- There is reasonable content on the page (see: No Content)
- I have read and accepted the Terms and Conditions
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi there!
❌ Before we can accept your domain request, you need to create a file named CNAME
in the root of your github pages site (this may not be the root of your repository). 📝
This file should contain a single line with the full js.org domain you are requesting, in this instance storelocator.js.org
.
Hello @MattIPv4, The I use GitHub Actions to deploy GitHub Pages, so this is linked to a branch. The last deployment job contains an artifact with the content of the website and the "CNAME" file is present Let me know if I need to make any other changes. Thanks! |
Ah, if you're using the new Actions workflow way of deploying I believe you don't need the CNAME file, you just need to set the subdomain in your settings. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
✅ Commit valid, CNAME present, site appears to have content *
* based off https://github.com/storelocatorjs/storelocatorjs.github.io/tree/main/docs
I've already added your requested subdomain to JS.ORGs zonefile. But as you are using a workflow to deploy the page there may be other steps involved to get the CNAME working. FYI: |
@indus I changed the deployment to use a branch as a trigger and the website is available. I have some questions:
Thanks |
I don't have a clear answer to any of the three questions. Everything was easy without workflows They made the process complicated. I would suggest to just try different settings until it works ;-) Sorry
|
I know other folks in the past have got stuck with the Actions workflow. Every time I have recommended reaching out to GitHub Support, as I suspect this is a breakage in this new style of deployment, yet I don't think anyone has. If you aren't able to get it to work toggling settings, I will once again recommend reaching out to support and see what they say :) |
@yoriiis I've just checked your page and it looks ok to me: https://storelocator.js.org |
@indus Yes it is ok, you can merge. Thanks for the support. I will check with the GitHub support if needed |
Welcome https://storelocator.js.org |