Redirect on changing user and organization name #4562

New Issue

GiteaMirror · 2025-11-02T05:54:41-06:00

GiteaMirror commented

2025-11-02 05:54:41 -06:00

Originally created by @kasbah on GitHub (Dec 28, 2019).

Currently gitea redirects repository URLs when you change the repository name (implemented in https://github.com/go-gitea/gitea/pull/807), but if you change a username or organization name then gitea won't redirect.

I am just wondering if there is interest in having redirects on username and organization name change implemented as well.

Originally created by @kasbah on GitHub (Dec 28, 2019). Currently gitea redirects repository URLs when you change the repository name (implemented in https://github.com/go-gitea/gitea/pull/807), but if you change a username or organization name then gitea won't redirect. I am just wondering if there is interest in having redirects on username and organization name change implemented as well.

GiteaMirror added the type/proposal label 2025-11-02 05:54:41 -06:00

GiteaMirror closed this issue

2025-11-02 05:54:42 -06:00

GiteaMirror commented

2025-11-02 05:54:42 -06:00

@lafriks commented on GitHub (Dec 29, 2019):

That is tricky one as somebody can create org or user with old name so it would not be consistent and could lead to potential problems

@lafriks commented on GitHub (Dec 29, 2019): That is tricky one as somebody can create org or user with old name so it would not be consistent and could lead to potential problems

GiteaMirror commented

2025-11-02 05:54:42 -06:00

@kasbah commented on GitHub (Dec 29, 2019):

There is a similar problem for just changing repository names that was already solved in #807 I believe. The solution is to not redirect when a new org/user takes the old name. This is also how Github does it.

If the new owner of your old username creates a repository with the same name as your repository, that will override the redirect entry and your redirect will stop working.

@kasbah commented on GitHub (Dec 29, 2019): There is a similar problem for just changing repository names that was already solved in #807 I believe. The solution is to not redirect when a new org/user takes the old name. This is also [how Github does it](https://help.github.com/en/github/setting-up-and-managing-your-github-user-account/changing-your-github-username#repository-references). > If the new owner of your old username creates a repository with the same name as your repository, that will override the redirect entry and your redirect will stop working.

GiteaMirror commented

2025-11-02 05:54:43 -06:00

@lunny commented on GitHub (Jan 1, 2020):

@lafriks What's the problems? But we have implemented the redirects when you change repository name.

@lunny commented on GitHub (Jan 1, 2020): @lafriks What's the problems? But we have implemented the redirects when you change repository name.

GiteaMirror commented

2025-11-02 05:54:43 -06:00

@lafriks commented on GitHub (Jan 1, 2020):

No problem, could be some risks but I'm fine if someone sends PR for this

@lafriks commented on GitHub (Jan 1, 2020): No problem, could be some risks but I'm fine if someone sends PR for this

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#4562