Stack for Repositories

[Neodevils]

🏷️ Discussion Type

Product Feedback

Body

When organizations have bunch of repositories but they are tied to each other somehow, it would be nice to have a stack (under of a category) where organization members / visitors can see the complete stack of app—or whatever they are building under a hood. Which makes the repository organization more clean, even dead repositories can be stay under a stack so they get recognition too.

[xop01]

GitHub has no stack or folder of repositories. The organization list is one flat list, including for Enterprise.

What you can do with that list:

• Topics. On each repo, About, then Topics. On the org Repositories page, search topic:your-stack. Topic names are public even on a private repo.
• Custom properties. In the org settings, add a property such as stack, set the same value on each repo in the group, then filter the repository list with prop.
• A shared name prefix so the default sort keeps them together.
• One repo whose README links the others, if you want a page a visitor can open.

A team groups who has access. It does not add a folder to the repository list.

@Neodevils

[Neodevils]

Of course, I know those things.

Well, same goes for the labels. Where you can create "effort/medium" but hey there is Issue Fields now which is doing exactly what you used to with labels.

So, keep your AI reply to yourself man. Thanks you. I'm not new to GitHub.

This was a suggestion.

Sincerely,
Neodevils.

[xop01]

Taking 1 additional minute of my precious time to answer you here, your AI (using the EM dash in your post) used the wrong labels unless it is you who struggles with clicking buttons which is why my AI answered it to try and enlighten yours

If you are not new to GitHub you might wish to learn a little more about it

Sincerely,
xop.

[Neodevils]

This is literally under Product Feedback. The entire premise of submitting feedback is proposing native features that do not exist yet, not asking someone to list existing workarounds

Also, Option + Shift + Hyphen exists on a Mac keyboard. You do not need an LLM to use punctuation

Have a good day

[Workdigi]

I think the useful part of this suggestion is that the “stack” would be a first class relationship between repositories, rather than another way of tagging or filtering them.

For example, an organization could define a stack such as:

Frontend → API → Backend → Infrastructure → Documentation

Each repository could belong to one or more stacks, and GitHub could show that relationship directly on the organization page. That would make it much easier for someone discovering the organization to understand how the repositories fit together, without having to open a README or already know the naming convention.

I also like the point about archived or inactive repositories. They could remain visible as part of the stack while clearly marked as inactive, instead of becoming disconnected from the project history.

Topics, properties and naming conventions are useful workarounds, but they do not really provide the visual project structure you are suggesting. I think that distinction makes this a reasonable feature request.

[Neodevils]

Finally someone gets me 😭

[Neodevils]

Any plans for this?