Find unused forks #4993

New Issue

GiteaMirror · 2025-11-02T06:10:21-06:00

GiteaMirror commented

2025-11-02 06:10:21 -06:00

Originally created by @sefsh on GitHub (Mar 3, 2020).

I've a bunch of user-created forks of a large repo. Some of the forks seem completely unused and thus only takes up space for no benefit. How can I find the all unused forks for removal?

Originally created by @sefsh on GitHub (Mar 3, 2020). I've a bunch of user-created forks of a large repo. Some of the forks seem completely unused and thus only takes up space for no benefit. How can I find the all unused forks for removal?

GiteaMirror added the type/enhancement issue/stale labels 2025-11-02 06:10:21 -06:00

GiteaMirror closed this issue

2025-11-02 06:10:22 -06:00

GiteaMirror commented

2025-11-02 06:10:22 -06:00

@guillep2k commented on GitHub (Mar 3, 2020):

Well, forks are repositories created by users at their discretion. Depending on your site policies (e.g. a company?) it's difficult to establish what is unused and what is not.

Having said that, the API will probably give you the flexibility you're looking for. Also, the /admin/repos page (sorted by least recently updated) might help too.

@guillep2k commented on GitHub (Mar 3, 2020): Well, forks are repositories created by users at their discretion. Depending on your site policies (e.g. a company?) it's difficult to establish what is unused and what is not. Having said that, the API will probably give you the flexibility you're looking for. Also, the `/admin/repos` page (sorted by least recently updated) might help too.

GiteaMirror commented

2025-11-02 06:10:22 -06:00

@sefsh commented on GitHub (Mar 7, 2020):

Yes, it's a user choice. For this instance's purpose however, there's no need in keeping unused forks around and I can free space instead.

I'm not familiar with the API but it sounds like I have to dive into it because the admin UI doesn't give enough information regarding this.

Come to think of it, I would like this as an action in the "Maintenance Operation" section called something like "Delete all unused forks". So now it's a feature request too. 🙂

@sefsh commented on GitHub (Mar 7, 2020): Yes, it's a user choice. For this instance's purpose however, there's no need in keeping unused forks around and I can free space instead. I'm not familiar with the API but it sounds like I have to dive into it because the admin UI doesn't give enough information regarding this. Come to think of it, I would like this as an action in the "Maintenance Operation" section called something like "Delete all unused forks". So now it's a feature request too. 🙂

GiteaMirror commented

2025-11-02 06:10:23 -06:00

@guillep2k commented on GitHub (Mar 7, 2020):

@yusf You'll find the API pretty convenient. Just check: https://try.gitea.io/api/swagger

(also present in your Gitea installation, in the footer, API link). 😁

@guillep2k commented on GitHub (Mar 7, 2020): @yusf You'll find the API pretty convenient. Just check: https://try.gitea.io/api/swagger (also present in your Gitea installation, in the footer, `API` link). 😁

GiteaMirror commented

2025-11-02 06:10:23 -06:00

@sefsh commented on GitHub (Mar 11, 2020):

Also, Commit Graph to the rescue 🎉

@sefsh commented on GitHub (Mar 11, 2020): Also, Commit Graph to the rescue 🎉

GiteaMirror commented

2025-11-02 06:10:23 -06:00

@stale[bot] commented on GitHub (May 10, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (May 10, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

GiteaMirror commented

2025-11-02 06:10:23 -06:00

@stale[bot] commented on GitHub (May 24, 2020):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (May 24, 2020): This issue has been automatically closed because of inactivity. You can re-open it if needed.

GiteaMirror commented

2025-11-02 06:10:24 -06:00

@stale[bot] commented on GitHub (Jul 25, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (Jul 25, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

GiteaMirror commented

2025-11-02 06:10:24 -06:00

@stale[bot] commented on GitHub (Aug 9, 2020):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Aug 9, 2020): This issue has been automatically closed because of inactivity. You can re-open it if needed.

GiteaMirror referenced this issue

2025-11-02 14:12:58 -06:00

[PR #4993] [MERGED] Backport: Fix layout of the topics editing form (#4971) #17581

Sign in to join this conversation.