Skip to content
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

Merged
merged 1 commit into from
Jul 12, 2023
Merged

storelocator.js.org #8364

merged 1 commit into from
Jul 12, 2023

Conversation

yoriiis
Copy link
Contributor

@yoriiis yoriiis commented Jul 10, 2023

Copy link
Member

@MattIPv4 MattIPv4 left a 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.

@MattIPv4 MattIPv4 added the awaiting CNAME This PR is waiting for the target to add a CNAME file label Jul 11, 2023
@yoriiis
Copy link
Contributor Author

yoriiis commented Jul 11, 2023

Hello @MattIPv4,

The CNAME file is already present
https://github.com/storelocatorjs/storelocatorjs.github.io/blob/main/docs/CNAME

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
https://github.com/storelocatorjs/storelocatorjs.github.io/actions/runs/5513367345

Let me know if I need to make any other changes. Thanks!

Docs: https://docs.github.com/en/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site#publishing-with-a-custom-github-actions-workflow

@MattIPv4
Copy link
Member

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.

Copy link
Member

@MattIPv4 MattIPv4 left a 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

@MattIPv4 MattIPv4 added add This PR/issue is regarding adding a new subdomain organisation This PR/issue is regarding a target on a GitHub organisation and removed awaiting CNAME This PR is waiting for the target to add a CNAME file labels Jul 11, 2023
@indus indus added the error The page requested returns an error label Jul 11, 2023
@indus
Copy link
Member

indus commented Jul 11, 2023

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:
#7853 (comment)
#8364 (comment)

@yoriiis
Copy link
Contributor Author

yoriiis commented Jul 11, 2023

@indus I changed the deployment to use a branch as a trigger and the website is available.

I have some questions:

  1. Can I go back to GitHub Action mode? If I understand correctly, this manipulation was just to "activate" the site
  2. Is the https checkbox available?
    image
  3. I also have another domain with your extension (thanks by the way :)), I had made the request when I was using Github Pages with a branch then I changed it to use GitHub Action. Deployment works but there is a DNS warning
    image

Thanks

@indus
Copy link
Member

indus commented Jul 11, 2023 via email

@MattIPv4
Copy link
Member

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 :)

@indus
Copy link
Member

indus commented Jul 12, 2023

@yoriiis I've just checked your page and it looks ok to me: https://storelocator.js.org
Do you think it is ok now or do you wnat to change something and wait with th merge?

@yoriiis
Copy link
Contributor Author

yoriiis commented Jul 12, 2023

@indus Yes it is ok, you can merge. Thanks for the support. I will check with the GitHub support if needed

@indus indus removed the error The page requested returns an error label Jul 12, 2023
@indus
Copy link
Member

indus commented Jul 12, 2023

Welcome https://storelocator.js.org

@indus indus merged commit eab8a01 into js-org:master Jul 12, 2023
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
add This PR/issue is regarding adding a new subdomain organisation This PR/issue is regarding a target on a GitHub organisation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants