Please change the name of the project to lispcookbook! (so the address https://lispcookbook.github.io/ is valid)

[daninus14]

Hi,

Can you please change the name of the repository to be lispcookbook.github.io??

That way the address will be https://lispcookbook.github.io/ instead of https://lispcookbook.github.io/

It's a bit annoying every time my browser navigates to the https://lispcookbook.github.io/ instead of https://lispcookbook.github.io/cl-cookbook/, specially when there are no links there to go to the correct page...

Thanks!

[vindarel]

I just talked about this with a friend yesterday; it may be too late to rename the GH pages project but we can create another Github pages repo with a meta redirect in its index.

[daninus14]

I think the only issues with renaming a repository are related to github actions, everything else including issues, wikis, followers, stars, and probably forks will stay. See https://docs.github.com/en/repositories/creating-and-managing-repositories/renaming-a-repository

From what I can see the actions you have are funding, which doesn't seem to be dependent on a name (unless I got it wrong) and the build pages, which is the whole point of the rename.

I thought many times before to submit this issue but refrained from doing so, but it really only takes a sec, that's why I asked.

[daninus14]

I think even if you go to the old repo in github like github.com/user/oldrepo it will redirect the user and even the git clone to the new repo

[vindarel]

What about the deployed pages?

https://lispcookbook.github.io/cl-cookbook/getting-started.html

would become

https://lispcookbook.github.io/getting-started.html

right?

[daninus14]

yeah, I think so. Ah are you worried about all the links around the web pointing to the previous URL?

[vindarel]

yes. So it's better to add a lispcookbook.github.io project with an index that redirects to the existing one.

[pnathan]

Agreed.

Back when this was a Sourceforge project, it's URL was https://cl-cookbook.sourceforge.net/ . After some 17 years since the last Sourceforge Changelog entry, I think it's absolutely fine to migrate.

Kind of wondering if there's a way to do a HTTP 302 to the new name.

On Tue, Oct 29, 2024, 8:35 AM vindarel @.***> wrote:

yes. So it's better to add a lispcookbook.github.io project with an index that redirects to the existing one.

— Reply to this email directly, view it on GitHub https://github.com/LispCookbook/cl-cookbook/issues/562#issuecomment-2444635105, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFZZYA3EFSDEUHUSVM74R3Z56TMHAVCNFSM6AAAAABQYHKIECVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBUGYZTKMJQGU . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[daninus14]

I wonder if in the github actions build workflow, whenever you push to the project, you can make it push as well to the other repository as well. That way one repo will be a mirror of the other, which will get pushed to every time there is a push in the first repository. Each repo will have the regular github action build github pages setup, so everything would work well.

That way, since it doesn't look like redirecting is possible, at least the content will be all the same.