Subgroups in Gitea #10786

New Issue

GiteaMirror · 2025-11-02T09:18:08-06:00

GiteaMirror commented

2025-11-02 09:18:08 -06:00

Originally created by @gruselglatz on GitHub (May 5, 2023).

Feature Description

Since 9.0 GitLab allows to create subgroups for groups/organizations, It would be great if we could do the same in Gitea.

Subgroups Docs: https://docs.gitlab.com/ce/user/group/subgroups/

We would like to organize our Repos in Subgroups like in Gitlab but i think the old Issue is dead?
Could we reevaluate the feature pls, I think it would be a great addition to Gitea.
https://github.com/go-gitea/gitea/issues/1872

Screenshots

No response

Originally created by @gruselglatz on GitHub (May 5, 2023). ### Feature Description Since 9.0 GitLab allows to create [subgroups for groups/organizations](https://about.gitlab.com/2017/03/22/gitlab-9-0-released/#subgroups-ce-ee), It would be great if we could do the same in Gitea. Subgroups Docs: https://docs.gitlab.com/ce/user/group/subgroups/ We would like to organize our Repos in Subgroups like in Gitlab but i think the old Issue is dead? Could we reevaluate the feature pls, I think it would be a great addition to Gitea. https://github.com/go-gitea/gitea/issues/1872 ### Screenshots _No response_

GiteaMirror added the type/proposal type/feature issue/duplicate labels 2025-11-02 09:18:08 -06:00

GiteaMirror closed this issue

2025-11-02 09:18:08 -06:00

GiteaMirror commented

2025-11-02 09:18:09 -06:00

@KN4CK3R commented on GitHub (May 5, 2023):

The other issue is not dead. Just nobody works on it.

Let's stay to the topic, this is not place for discussion. If you have nothing to add that would contribute to implementing this feature in Gitea, just add reaction to issue. Otherwise if you want to see this issue fixed you will have to wait, implement yourself or pay someone to implement this for you.

https://github.com/go-gitea/gitea/issues/1872#issuecomment-1263720465

@KN4CK3R commented on GitHub (May 5, 2023): The other issue is not dead. Just nobody works on it. > Let's stay to the topic, this is not place for discussion. If you have nothing to add that would contribute to implementing this feature in Gitea, just add reaction to issue. Otherwise if you want to see this issue fixed you will have to wait, implement yourself or pay someone to implement this for you. https://github.com/go-gitea/gitea/issues/1872#issuecomment-1263720465

GiteaMirror commented

2025-11-02 09:18:09 -06:00

@delvh commented on GitHub (May 5, 2023):

Well…
To be fair, an issue is pretty dead if the conversation is locked.
If I were a user looking at this issue, I'd think too that the issue is dead.

@delvh commented on GitHub (May 5, 2023): Well… To be fair, an issue is _pretty_ dead if the conversation is locked. If I were a user looking at this issue, I'd think too that the issue is dead.

GiteaMirror commented

2025-11-02 09:18:09 -06:00

@gruselglatz commented on GitHub (May 8, 2023):

@KN4CK3R The issue is/was basically dead. I couldn't Create a comment, or Upvote for it. The issue is linked on the official Website in the Feature list. So it seemed pretty important. And it seems strange to only give the normal "open-source" answer: Do it on your own or don't complain.

So thanks for Reopening the Issue and as i am no Go Programmer I have to apologize that I cant implement this feature on my own, which seems pretty important to a bunch of people.

@gruselglatz commented on GitHub (May 8, 2023): @KN4CK3R The issue is/was basically dead. I couldn't Create a comment, or Upvote for it. The issue is linked on the official Website in the Feature list. So it seemed pretty important. And it seems strange to only give the normal "open-source" answer: Do it on your own or don't complain. So thanks for Reopening the Issue and as i am no Go Programmer I have to apologize that I cant implement this feature on my own, which seems pretty important to a bunch of people.

GiteaMirror commented

2025-11-02 09:18:09 -06:00

@KN4CK3R commented on GitHub (May 8, 2023):

I didn't know you can't vote in locked issues but besides that this issue does not add something of value I think. We are still aware of the other issue but noone is currently implementing or planning it.

@KN4CK3R commented on GitHub (May 8, 2023): I didn't know you can't vote in locked issues but besides that this issue does not add something of value I think. We are still aware of the other issue but noone is currently implementing or planning it.

GiteaMirror commented

2025-11-02 09:18:09 -06:00

@gruselglatz commented on GitHub (May 8, 2023):

It added the value of reopening this other important issue. ;)

@gruselglatz commented on GitHub (May 8, 2023): It added the value of reopening this other important issue. ;)

GiteaMirror commented

2025-11-02 09:18:10 -06:00

@lunny commented on GitHub (May 8, 2023):

I have unlocked that issue #1872.

@lunny commented on GitHub (May 8, 2023): I have unlocked that issue #1872.

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#10786