Closed hober closed 5 months ago
There is a way to do the redirect. We'll need to add a file in w3c.github.io.
There is a way to do the redirect.
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.
There is a way to do the redirect.
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. W3C Proxy still needs to be updated to use directly w3c.github.io/process
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 <process.w3c.github.com>
mailinst list instead of <w3process.w3c.github.com>
.
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
@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.
Sure. Does github.io do redirects if we rename the repo, or would we break a bunch of links?