You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, it seems a js.org subdomain that was requested to target this repository no longer works.
The subdomain requested was paraiba.js.org and had the target of paraibajs.github.io.
It produced the following failures when tested as part of the cleanup:
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:
JS.ORG CLEANUP
Hello, it seems a
js.org
subdomain that was requested to target this repository no longer works.The subdomain requested was
paraiba.js.org
and had the target ofparaibajs.github.io
.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: