Add option to delete repo if it is broken #7889

Closed
opened 2025-11-02 07:40:27 -06:00 by GiteaMirror · 7 comments
Owner

Originally created by @6543 on GitHub (Sep 23, 2021).

If a repo is broken somehow. you will just see a 500 page without the option to delete it.

you can manually add /settings to go to repo settlings page to delete it, but most people don't know.

So I propose a button to directly delete it.

Originally created by @6543 on GitHub (Sep 23, 2021). If a repo is broken somehow. you will just see a 500 page without the option to delete it. you can manually add `/settings` to go to repo settlings page to delete it, but most people don't know. So I propose a button to directly delete it.
GiteaMirror added the type/proposaltype/enhancement labels 2025-11-02 07:40:27 -06:00
Author
Owner

@delvh commented on GitHub (Sep 23, 2021):

How do you break a repo in the first place?
I support your request, but I definitely wonder what you have to do to achieve that…

@delvh commented on GitHub (Sep 23, 2021): How do you break a repo in the first place? I support your request, but I definitely wonder what you have to do to achieve that…
Author
Owner

@6543 commented on GitHub (Sep 24, 2021):

https://fosstodon.org/@5am/106979181347005295

It should not hapen ... but there is real world

@6543 commented on GitHub (Sep 24, 2021): https://fosstodon.org/@5am/106979181347005295 It should not hapen ... but there is real world
Author
Owner

@wxiaoguang commented on GitHub (Sep 24, 2021):

Where should the link be put to, is there any recommended page/location?

@wxiaoguang commented on GitHub (Sep 24, 2021): Where should the link be put to, is there any recommended page/location?
Author
Owner

@lunny commented on GitHub (Sep 24, 2021):

You can delete it from admin panel currently.

@lunny commented on GitHub (Sep 24, 2021): You can delete it from admin panel currently.
Author
Owner

@nolash commented on GitHub (Oct 18, 2021):

I got a broken one due to network issues when trying to migrate from a gitlab repo

@nolash commented on GitHub (Oct 18, 2021): I got a broken one due to network issues when trying to migrate from a gitlab repo
Author
Owner

@delvh commented on GitHub (Oct 18, 2021):

Ah, I just noticed a very valid use-case I myself have already encountered and where I already thought about opening an issue:
On my local instance that I use to test Gitea features, I've set my repo dir to be /tmp, so that it will automatically be cleaned when I shutdown my computer.
When I restart Gitea after that, the repo is gone, as expected, but the db does not know about it, and hence I get exactly the described broken state where I cannot do anything with the repo.

@delvh commented on GitHub (Oct 18, 2021): Ah, I just noticed a very valid use-case I myself have already encountered and where I already thought about opening an issue: On my local instance that I use to test Gitea features, I've set my repo dir to be `/tmp`, so that it will automatically be cleaned when I shutdown my computer. When I restart Gitea after that, the repo is gone, as expected, but the db does not know about it, and hence I get exactly the described broken state where I cannot do anything with the repo.
Author
Owner

@delvh commented on GitHub (Nov 22, 2021):

Closed in #17747.

@delvh commented on GitHub (Nov 22, 2021): Closed in #17747.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#7889