GitLab 9.0 now allows to create subgroups for groups/organizations, It would be great if we could do the same in Gitea.
Does Teams provide some or all of this functionality? What is missing from Teams?
Teams would not provide "endless" nested groups 馃檨
In any case, this would require a large rewrite of how we're handling Organizations today (GitLab put _a lot_ of time into Subgroups...) and would not be backwards compatible (hence why Subgroups in GitLab was introduced in a Major release so breaking changes was allowed 馃檪 )
And to better answer @razzintown, Teams can't have repositories.
Let me know if my understanding is correct:
Teams can't have repositories.
- Repositories may be assigned to one or more teams.
- Repositories may be set to private to prevent other teams from seeing them.
Teams would not provide "endless" nested groups :slightly_frowning_face:
- Team names may contain a dash to give the appearance of nested groups, i.e. "company-department", "company-department-managers", etc.
Since multiple teams may share a private repo, is there any other functionality missing?
Sub-groups are not only about permissions, but structure as well. Say you have an Orga with a total of 300 repos over 30 teams, there's no way to structure that w/o proper "folders" (sub-groups).
So in the end you end up with orga/team30/repo10
instead of orga/repo300
In any case, this would break a lot of existing stuff _and_ be a major overhaul so I'm setting this for 2.0 for now
This would automatically give us the pastebin/gist feature #693 as well, or any related idea, since some nested names could be reserved for those features like giteaUser/gist
or giteaUser/pastebin
just off the top of my head, or with a dot prefix if that's legal with git, not sure. It would also allow users to create new repos progamatically with permissions already set by the parent 'space'.
It could also eventually allow federation since it basically boils down to automagic merging, and using mirrors nested in reserved namespace would allow for manual conflict resolution as fallback without polluting the root namespace with lots of mirrors.
We org our git projects into groups of bounded contexts. Where the git repo is, informs the purpose, scope, and communication channels, as well as the authorization to the project. subgorups can be valuable.
Is there any estimable timeline when this could potentially be implemented? This would be super useful.
@Th3Whit3Wolf No people are working on this.
Still no update?
dont see any
I use Gitea for myself and Gitlab for team work. In Gitlab we have subgroups containing a lot of repos. That's what's keeping us from migrating. This possibility in Gitea would be really great.
Is this feature is planned?
It is planed but nobody does work on this currently
Ok thanks for the confirmation
Currently this feature is already available in Github
Most helpful comment
It is planed but nobody does work on this currently