Grouping support for repositories

[yawn]

For accounts with >100 repositories it would a great help it we could get grouping support / the ability to organize the list repositories in hierarchies e.g. by

• customer
• programming language
• activity (commits available for the last 4 weeks)
• the current filters (Mirrors, Forks, Sources, Private, Public)

As a starting point it would help tremendously if the repository list view would split repositories into hierarchies by splitting on ., e.g. for the repositories:

• Acme.DemoProject
• Acme.FancyApp
• FooCorp.NextCoolThing

+ Acme
    DemoProject
    FancyApp
- FooCorp

[patcon]

Interesting ideas. Could this request be merged with #49?

[patcon]

Also, this might be a prime candidate for a userscript solution. (see #128)

@isaacs, still waiting to hear if you think a tag for userscript fixes might be helpful in making this issue queue more obviously actionable :)

[yawn]

#49 is a similar problem, yes, only the other way around. They would like to migrate from many organizations to one, we just have many projects for different customers under one organization and would like to have "virtual" organizations underneath that.

Maybe that's the way to go? Just add the ability to add virtual sub-organizations to your account with virtual meaning:

• Semantics stay the same / UI does not need chnging
• Some information is read-only and is taken from the parent
• You can convert an organization into a non-virtual one (and vice versa)
• Virtual organizations always belong to the same parent organization (= the paid account)

For simplicities sake it would be sufficient to limit the depth of this tree to 2 (root + any number of children).

[harrism]

As creator of #49 I think the goal is really the same -- grouping / hierarchy in repositories under an org, regardless of which way you are coming at it. If we consolidate all of our orgs/projects, we will have many projects under one organization, which is the same problem @yawn describes.

[quantuminformation]

Would love to see this.

[MalcolmAnderson]

Ditto - I'm taking a class right now and I'd like to have all of my class projects under a single "directory"
Has this been solved in the 4 years since the original post?

[jpierson]

Having labels/tags at the repository level may even be more powerfull so that arbitrary overlapping groupings are possible. This may also make some forms of automation similar to those that work off of git tags possible where a set of repositories is selected on the basis of association with a given label/tag.

[damijanc]

Any update on this?

[SimyungYang]

+1

[mathieu-b]

+1

[matthijskooijman]

Having labels/tags at the repository level may even be more powerfull so that arbitrary overlapping groupings are possible.

Note that would not be a complete replacement of hierarchical grouping, since the latter can be shown in the repository urls instead of just on the github web interface.

(also, please refrain from posting +1 comments, rather use the thumbs-up on the initial post)

[JMPZ]

Is this dead? I would love to have this!

[Levi-Lesches]

community/community#4174 is the corresponding issue in the official GitHub feedback repository (this repo is not official).

Also, #1233 asks for the ability to sort starred repos, and community/community#4470 is the official discussions page for that.