search

go-gitea / gitea

Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD
https://gitea.com
MIT License
43k stars 5.31k forks source link

Categories and organization for repos #31467

Open Ratstail91 opened 1 week ago

Ratstail91 commented 1 week ago

Feature Description

It would be useful if gitea supported a way to tag/label/group repos for easier searching and management.

i.e. Last night, I realized I didn't have an easy way to group about a dozen repos together in my org, so I ended up making a new org to hold them. These repos could be considered a related "set", but I didn't have an easy way to search for them specifically, or filter them out when they aren't needed - making a separate org felt like a stopgap.

Neither github or gitea have this feature, so I'd figured I'd ask how hard it would be to implement. Thanks in advance!

Screenshots

No response

a1012112796 commented 1 week ago

looks star lists is what you need https://github.com/go-gitea/gitea/pull/27179

makar112233 commented 1 week ago

@Ratstail91 we've used "Locations" for it. May be you can try the same scheme?

Ratstail91 commented 3 days ago

looks star lists is what you need #27179

Not quite, that looks more like a way to organize bookmarks.

@Ratstail91 we've used "Locations" for it. May be you can try the same scheme?

I'm not sure what you mean by "location", @makar112233.

makar112233 commented 2 days ago

@Ratstail91 we used this "locations" as an alternative for plugin "categories" in BitBucket. image

Ratstail91 commented 1 day ago

@makar112233 That's uhh... creative?

These location settings only apply to orgs, I want to organize and group the repos - the best way to do that is with an org, which just brings back the same issue.

This is definitely a feature that would be useful, that neither github or gitea seem to have. I think one or more tags on a repo would make domain cross-cutting issues easier to manage on a large scale, as well.

If I knew go, I'd crack open the codebase to see what would be needed. As it is, it's a blindspot for me, and I've got other priorities - but I'd love to see someone add this as a feature!