ORG: Repository Organization.

[MichelDiz]

Feature Description

As we grow an organization, we inevitably accumulate numerous repositories. While we do use the search field to find a specific repo, the lack of organization – be it by theme, category, or some other division – can make the experience both unsightly and challenging to manage.

I suggest implementing a branching system for repositories, perhaps categorizing them or something similar. If we had categories like "Clients", "Customer Success", "Tutorials", etc., it would be much easier to manage. Moreover, it would assist users in discovering relevant repositories.

Screenshots

No response

[lunny]

I think repositories have supported topic, maybe a filter with topic could resolve your problem.

[MichelDiz]

Thanks, but that's not ideal. The ideal is have a segregation of repositories.

A cluttered list of repositories can be overwhelming and not very user-friendly. While filtering can be a solution, it doesn't provide the visual organization that many users find intuitive. When people are exploring a repository they stumbled upon, they often don't know where exactly to look. Many organizational repositories can appear as a chaotic dump of old and unmaintained projects.

Navigating through thousands of repositories and not being sure whether to delete or migrate specific ones can be daunting. It's frustrating to see a vast amount of content and not understand its original purpose, forcing the team to investigate each repository individually. Additionally, many people might disregard an old repository as non-functional simply because it's at the bottom of the list.

A structured list, similar to categorized folders, would be much more beneficial in such cases. This would not only enhance visual clarity but also streamline the exploration and maintenance processes for both new and experienced users.

[plashenkov]

There are also:

• https://github.com/go-gitea/gitea/issues/1872
• https://github.com/go-gitea/gitea/issues/24542

[plashenkov]

Honestly, I believe this is a very important feature. But only GitLab currently has this.

[plashenkov]

Probably a monorepo approach can be used as a workaround for now.

[eeyrjmr]

Iirc there is another feature request for this very interesting capability

[MichelDiz]

@plashenkov that's pretty old request!

I just checked out the Gitlab feature. It seems more complex in terms of permissions and stuff. I think just having a nesting logic would be enough. An "Org that holds Orgs". That would replicate the logic easily.

[plashenkov]

@MichelDiz I also think that nesting would be enough.

[wangyan]

This is a very useful function and it is needed.

[KlavsKlavsen]

IMHO the "easiest" and "good enough" method - would be to add a "team/project" option for repositories. If they have that set (under settings) - they're NOT shown in the "default list" for the org - but instead the project is shown (and when clicked - it acts as a filter - to only show repositories added to that project). WDYT ?

@lunny would you accept a PR for this? (re-using existing projects - simply adding a 'belongs to team' setting to repositories - and adjusting the repository listing on "org main page" ?) - or would you prefer 'project'.. or maybe both options team+project? (and if so - should they be mutually exclusive?)

[lunny]

I think teams have already supported special repositories. And non-team private repositories will not be displayed. Is that enough?