Add subgroups #4837
Replies: 77 comments 7 replies
|
I'm interested in this issue. Has someone at Github seen this and has this idea been considered? |
|
bump |
|
This feature is a must. |
|
bump |
|
bump |
|
bump |
|
bump |
|
bump |
|
bump |
|
bump |
|
bump |
|
bump |
|
bump |
|
bump |
|
+1 |
|
+1 |
|
+1 |
|
+1 |
|
any news here ? |
|
Bump +1 |
|
Seems that mickeysoft does not care, unless you pay for it. So the only viable thing is to prefix any forked repo's into the preferred group name and do some internal logic at your end... We will have Half Life 3 sooner than this feature. |
|
The lack of this feature is exactly why the org I work for will never move to GitHub and will keep using a competitors product. Just throwing that out there for the GitHub Execs to see that they're leaving money on the table by ignoring this one. |
|
In an "organization", not all projects are at the same flat layer, a "subgroup" concept is definitely necessary for better repo management. Cannot understand why this feature request is ignored for so long. |
|
+1 |
|
Microsoft is officially RETARDED. |
|
+1 |
|
How has it been so many years since this got opened and there wasn't even a statement on whether this is something that they'll implement in the future... this is beyond me. |
|
+1 |



Uh oh!
There was an error while loading. Please reload this page.
GitLab offers a thing called subgroups in their organization-like system. It allows grouping project repositories without the need to create multiple organizations.
This feature is really useful when managing projects and should really be implemented.
This could for example avoid GitHub creating multiple organizations (
cli,actions...). Those project could directly be ingithub!Subgroups could also have some global features (like webhooks, public/private views...) so new repositories in the group inherit the group settings.
All reactions