Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Subgroups in Gitea #24542

Closed
gruselglatz opened this issue May 5, 2023 · 6 comments
Closed

Subgroups in Gitea #24542

gruselglatz opened this issue May 5, 2023 · 6 comments
Labels
issue/duplicate The issue has already been reported. type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@gruselglatz
Copy link

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.
#1872

Screenshots

No response

@gruselglatz gruselglatz added type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first. labels May 5, 2023
@KN4CK3R
Copy link
Member

KN4CK3R commented 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.

#1872 (comment)

@KN4CK3R KN4CK3R closed this as completed May 5, 2023
@KN4CK3R KN4CK3R added the issue/duplicate The issue has already been reported. label May 5, 2023
@delvh
Copy link
Member

delvh commented 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.

@gruselglatz
Copy link
Author

@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.

@KN4CK3R
Copy link
Member

KN4CK3R commented 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.

@gruselglatz
Copy link
Author

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

@lunny
Copy link
Member

lunny commented May 8, 2023

I have unlocked that issue #1872.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/duplicate The issue has already been reported. type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Development

No branches or pull requests

4 participants