Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Labels/Tags for repositories #5171

Closed
michael-brade opened this issue Oct 25, 2018 · 7 comments
Closed

Labels/Tags for repositories #5171

michael-brade opened this issue Oct 25, 2018 · 7 comments
Labels
issue/duplicate The issue has already been reported.

Comments

@michael-brade
Copy link

Feature Request:

I would like to be able to assign labels or tags to repositories, just like you can assign labels to issues. Right now the only way to group repositories is by organization and per user. And the poor man's way is to prefix the repository name with a group name. It would be much nicer to be able to tag/label the repositories and then be able to filter them by label.

@techknowlogick techknowlogick added the issue/duplicate The issue has already been reported. label Oct 25, 2018
@techknowlogick
Copy link
Member

Closing as duplicate of #3711

See: https://blog.gitea.io/2018/08/gitea-1.5.0-is-released/ for a GIF of how to use topics.

@michael-brade
Copy link
Author

Oh gee, I just found exactly that! Sorry for this issue and thanks for being faster than me 😄

@michael-brade
Copy link
Author

Hmm, a nitpick: I am using 1.6.0-rc.1, but in that version the topics are always converted to lower case, so API becomes "api". Is that intentional or a bug? The GIF in your link doesn't do that.

@techknowlogick
Copy link
Member

I believe it is intentional. There was a PR (that was merged after the one I linked above) that does some validation, to reduce duplication of tags, and cleaning up of things. @axifive would be able to give you more specific information.

@lunny
Copy link
Member

lunny commented Oct 25, 2018

That maybe a bug. We should keep the original name of topic.

@michael-brade
Copy link
Author

So... should I open a new issue? Or rename and reopen this one?

@lunny
Copy link
Member

lunny commented Oct 29, 2018

@michael-brade I think open a new issue is better.

@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/duplicate The issue has already been reported.
Projects
None yet
Development

No branches or pull requests

3 participants