tree-cli.js.org

[yangshun]

• There is reasonable content on the page (see: No Content)
• I have read and accepted the Terms and Conditions
• The site content can be seen at https://yangshun.github.io/tree-node-cli/

The site content is documentation on how to use the tree-node-cli npm library (under the command tree)

[MattIPv4]

Hi there!

❌ Before we can accept your domain request, you need to configure your GitHub Pages site to use the requested js.org subdomain. Head to your repository settings, locate the Pages settings (under Code and Automation), and enter the js.org subdomain in the custom domain field. 📝

[indus]

I've already added your requested subdomain to JS.ORGs zonefile. But you still have to (re-)add a file named CNAME to your branch with the single line tree.js.org to make it work.
I'll merge after we have "contact". Please keep this PR open.

[yangshun]

I'm not sure why GitHub says tree.js.org is already taken when I try to configure it from my repo's pages setting. Visiting https://tree.js.org shows another site indeed. Perhaps from a previous entry?

Anyway I've added a CNAME file containing tree.js.org.

Thanks! @indus @MattIPv4

[indus]

@MattIPv4 Do you know why this is even possible when I add the subdomain like so:

I mean it clearly targets yangshun.github.io

@yangshun I think you will have to get in contact with GitHub and ask them to free the subdomain.

[MattIPv4]

GitHub can't see that it targets yangshun.github.io as it is proxied, and even if it wasn't all *.github.io just map to the same set of IPs. GitHub allows projects to claim custom subdomains on a first-come, first-served basis, and if there's a dispute, they then do additional verification via a TXT record I believe. Reaching out to support is the best way to kick that off from what I recall.

[yangshun]

Thanks guys, I'll just use tree-cli.js.org, it seems vacant.

[indus]

Welcome https://tree-cli.js.org