-
-
Notifications
You must be signed in to change notification settings - Fork 109
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
JS.ORG CLEANUP #419
Comments
@bendemboski @rwwagner90 I must've missed the memo. Are we having trouble with this? Keeping it? Dumping it? Looks like we've each taken a turn adding the
|
I submitted a PR to |
Ah, I see js-org/js.org#3556 |
We dropped the custom domain for now since it was not working. If we can get it to work, that would be great! |
Looks like this has been fixed. 8055347 |
JS.ORG CLEANUP
Hello, it seems a
js.org
subdomain that was requested to target this repository no longer works.The subdomain requested was
ember-electron.js.org
and had the target offelixrieseberg.github.io/ember-electron
.It produced the following failures when tested as part of the cleanup:
Failed with status code '404 Not Found'
Failed with status code '404 Not Found'
To keep the
js.org
subdomain you should add a page with reasonable content within a month so the subdomain passes the validation.Failure to rectify the issues will result in the requested subdomain being removed from JS.ORGs DNS and the list of active subdomains.
If you are wanting to keep the
js.org
subdomain and have added reasonable content, YOU MUST reply to the main cleanup issue with the response format detailed at the top to keep the requested subdomain.🤖 Beep boop. I am a robot and performed this action automatically as part of the js.org cleanup process. If you have an issue, please contact the js.org maintainers.
The text was updated successfully, but these errors were encountered: