-
Notifications
You must be signed in to change notification settings - Fork 120
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
repo name nit: it'd be nice if this were simply w3c/process #871
Comments
Sure. Does github.io do redirects if we rename the repo, or would we break a bunch of links? |
There is a way to do the redirect. We'll need to add a file in w3c.github.io. |
That link seems to be about something else: moving a repo from one org to another. Here, it's already in the right org, it just needs a name change. I think the redirects work automatically in that case, but I would like to be sure. |
I'm pretty confident that it will work but I'll double check nevertheless. |
ok. Renaming done. w3c.github.io are redirected. |
currently it looks like https://www.w3.org/Consortium/Process/Drafts/ is redirecting to github.io instead of proxying it. Or maybe it's proxying the old github.io address, and that is loading something that redirects to the new one |
PSA: a side effect I forgot to foresee: I needed to update my email filters, as github notifications are now sent via the |
@frivoal this will be taken care of at the same time as we introduce the new Process document URI per issue #729. |
Everything should be fine due to the renaming. #729 will be dealt with separately. |
No description provided.
The text was updated successfully, but these errors were encountered: