Repository topic/labeling globally and within an organisation #76

New Issue

GiteaMirror · 2025-11-02T03:07:46-06:00

GiteaMirror commented

2025-11-02 03:07:46 -06:00

Originally created by @typeless on GitHub (Nov 22, 2016).

When the number of repositories of an organisation grows to an extent, it's going to be difficult to keep the repos well-organised and easy to find. In directory-oriented VCS like Subversion, that can be intuitively handled by directory hierarchy. Something like labels for Git repository would help improving the user experience.

Ideas?

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Originally created by @typeless on GitHub (Nov 22, 2016). When the number of repositories of an organisation grows to an extent, it's going to be difficult to keep the repos well-organised and easy to find. In directory-oriented VCS like Subversion, that can be intuitively handled by directory hierarchy. Something like labels for Git repository would help improving the user experience. Ideas? <bountysource-plugin> --- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/39507145-repository-labeling-within-an-organisation?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github). </bountysource-plugin>

GiteaMirror added the type/feature type/proposal type/enhancement labels 2025-11-02 03:07:46 -06:00

GiteaMirror closed this issue

2025-11-02 03:07:47 -06:00

GiteaMirror commented

2025-11-02 03:07:47 -06:00

@tboerger commented on GitHub (Nov 24, 2016):

This needs to be optional for sure, Bitbucket is an example, they are providing some kind of folders now, but IMHO it's not done really good.

@tboerger commented on GitHub (Nov 24, 2016): This needs to be optional for sure, Bitbucket is an example, they are providing some kind of folders now, but IMHO it's not done really good.

GiteaMirror commented

2025-11-02 03:07:47 -06:00

@typeless commented on GitHub (Nov 25, 2016):

@tboerger What are the disadvantages of Bitbucket's approach? I have never used the feature at Bitbucket.

@typeless commented on GitHub (Nov 25, 2016): @tboerger What are the disadvantages of Bitbucket's approach? I have never used the feature at Bitbucket.

GiteaMirror commented

2025-11-02 03:07:47 -06:00

@lunny commented on GitHub (Feb 11, 2017):

This is like github topic.

@lunny commented on GitHub (Feb 11, 2017): This is like github topic.

GiteaMirror commented

2025-11-02 03:07:47 -06:00

@typeless commented on GitHub (Mar 28, 2017):

A tree-like directory view of repositories would still be useful than the Github topic (or they serve different purposes). For instance, we currently have dozens of small shared libraries which share a common umbrella to expose a set of APIs. It's similar to Qt and its subordinate modules. In order to avoid messing the libraries with other unrelated repos belonging to the same team, we could use sub-modules to emulate the tree view. But it would still require annoying linear-search from page to page to locate the meta repo if it's not on the first few pages. It's less optimal than what CVS/subversion can do when it comes to organize hierarchical relationships of projects.

@typeless commented on GitHub (Mar 28, 2017): A tree-like directory view of repositories would still be useful than the Github topic (or they serve different purposes). For instance, we currently have dozens of small shared libraries which share a common umbrella to expose a set of APIs. It's similar to Qt and its subordinate modules. In order to avoid messing the libraries with other unrelated repos belonging to the same team, we could use sub-modules to emulate the tree view. But it would still require annoying linear-search from page to page to locate the meta repo if it's not on the first few pages. It's less optimal than what CVS/subversion can do when it comes to organize hierarchical relationships of projects.

GiteaMirror commented

2025-11-02 03:07:48 -06:00

@marbetschar commented on GitHub (Mar 8, 2018):

Would really love to see GitHub like topics in Gitea! This would enable a bunch of possibilities. Was there already any progress in implementing this?

@marbetschar commented on GitHub (Mar 8, 2018): Would really love to see GitHub like topics in Gitea! This would enable a bunch of possibilities. Was there already any progress in implementing this? ![topics](https://user-images.githubusercontent.com/392542/37148180-c8318604-22c9-11e8-91ea-734f62e492ec.JPG)

GiteaMirror referenced this issue

2025-11-02 10:09:38 -06:00

schedule action task not work #12431

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#76