Transfer ownership of private repository to Organization HTTP404 #742

New Issue

GiteaMirror · 2025-11-02T03:34:51-06:00

GiteaMirror commented

2025-11-02 03:34:51 -06:00

Originally created by @Avalancs on GitHub (May 24, 2017).

Gitea version (or commit ref): ff2464c
Can you reproduce the bug at https://try.gitea.io:
- Yes

Description

I did this on try.gitea.io:

Make an Organization (AvalancsOrg)
Make a private repository (TestRepo)
Go to Settings
Transfer Ownership to the Org (AvalancsOrg)
Try to access the repository from the dashboard

Step 5 causes a HTTP404 to be shown istead of opening the repository. I did not push anything into the repository, so it should be empty.

Screenshot

The dashboard shows the transfer of the repository as my last step

Originally created by @Avalancs on GitHub (May 24, 2017). - Gitea version (or commit ref): ff2464c - Can you reproduce the bug at https://try.gitea.io: - [X] Yes ## Description I did this on try.gitea.io: 1. Make an Organization (AvalancsOrg) 2. Make a private repository (TestRepo) 3. Go to Settings 4. Transfer Ownership to the Org (AvalancsOrg) 5. Try to access the repository from the dashboard Step 5 causes a HTTP404 to be shown istead of opening the repository. I did not push anything into the repository, so it should be empty. ## Screenshot The dashboard shows the transfer of the repository as my last step ![ava_issue](https://cloud.githubusercontent.com/assets/18668703/26406247/04a1b740-4098-11e7-8047-e8133147d799.jpg)

GiteaMirror added the type/bug label 2025-11-02 03:34:51 -06:00

GiteaMirror closed this issue

2025-11-02 03:34:51 -06:00

GiteaMirror commented

2025-11-02 03:34:52 -06:00

@lunny commented on GitHub (May 26, 2017):

@Avalancs please confirm #1812 fix this issue.

@lunny commented on GitHub (May 26, 2017): @Avalancs please confirm #1812 fix this issue.

GiteaMirror commented

2025-11-02 03:34:52 -06:00

@camlafit commented on GitHub (May 26, 2017):

Tested and same error
I can't reopen this issue

@camlafit commented on GitHub (May 26, 2017): Tested and same error I can't reopen this issue

GiteaMirror commented

2025-11-02 03:34:52 -06:00

@Avalancs commented on GitHub (May 31, 2017):

As mentioned, issue is still reproducible in try.gitea.io with 0f5b399

@Avalancs commented on GitHub (May 31, 2017): As mentioned, issue is still reproducible in try.gitea.io with 0f5b399

GiteaMirror commented

2025-11-02 03:34:52 -06:00

@ethantkoenig commented on GitHub (Jun 2, 2017):

@Avalancs For a newly-created organization (i.e. an organization created when try.gitea.io was running 0f5b399), or for a organization that was created beforehand?

@ethantkoenig commented on GitHub (Jun 2, 2017): @Avalancs For a newly-created organization (i.e. an organization created when try.gitea.io was running 0f5b399), or for a organization that was created beforehand?

GiteaMirror commented

2025-11-02 03:34:52 -06:00

@Avalancs commented on GitHub (Jun 3, 2017):

It was the same organization I created with ff2464c but I created a new repository to test it again.

@Avalancs commented on GitHub (Jun 3, 2017): It was the same organization I created with ff2464c but I created a new repository to test it again.

GiteaMirror commented

2025-11-02 03:34:52 -06:00

@ethantkoenig commented on GitHub (Jun 3, 2017):

@Avalancs Without manually modifying the DB, there's no way to fix the problem for pre-existing organizations. If you try creating a new organization, the problem should be fixed.

@ethantkoenig commented on GitHub (Jun 3, 2017): @Avalancs Without manually modifying the DB, there's no way to fix the problem for pre-existing organizations. If you try creating a new organization, the problem should be fixed.

GiteaMirror commented

2025-11-02 03:34:53 -06:00

@Avalancs commented on GitHub (Jun 3, 2017):

Ahh, okay, good to know. I'll try it on tuesday when I can find my credentials... If you are certain that fixes the problem you can close the issue. Thanks for the explanation!

@Avalancs commented on GitHub (Jun 3, 2017): Ahh, okay, good to know. I'll try it on tuesday when I can find my credentials... If you are certain that fixes the problem you can close the issue. Thanks for the explanation!

GiteaMirror commented

2025-11-02 03:34:53 -06:00

@camlafit commented on GitHub (Jun 4, 2017):

Hi

Before to close, should be possible to get sql queries to act, or any
workaround ?
In some case could be not possible to create a new org, move all repo,
teams, user and delete old orga.

Thanks

@camlafit commented on GitHub (Jun 4, 2017): Hi Before to close, should be possible to get sql queries to act, or any workaround ? In some case could be not possible to create a new org, move all repo, teams, user and delete old orga. Thanks

GiteaMirror referenced this issue

2025-11-02 11:49:16 -06:00

[PR #742] [MERGED] Add units concept for modulable functions of a repository #15553

GiteaMirror referenced this issue

2025-11-02 11:52:38 -06:00

[PR #992] [MERGED] add missing copyright header #15701

Sign in to join this conversation.