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
If the transferred repository contains a GitHub Pages site, then links to the Git repository on the Web and through Git activity are redirected. However, we don't redirect GitHub Pages associated with the repository.
The only way to get technologyadvice.github.io/stardust to redirect to the new docs is to create a TechnologyAdvice/stardust repo with gh-pages site and an index.html that redirects to the new gh-pages site. The reason I do not want to do this, is that it will break the repo redirects since there will be an actual repo there. That means everyone's forks, remotes, and GitHub links will be broken.
I've considered adding TechnologyAdvice/stardust with a README.md that points users here. Then, also publish a gh-pages site with a redirect from the old docs to the new docs. Again, this would break GitHub links (forks, remotes), but perhaps that is actually better if we then save doc site users? Maybe people trying to use GitHub can find their way here easier than those trying to use the doc site.
@levithomason seems we missed something on migration, on old docs url - 404 😿
The text was updated successfully, but these errors were encountered: