Feature Request: Define superset of labels and selection of relevant ones for each repo #2737

Closed
opened 2025-11-02 04:46:12 -06:00 by GiteaMirror · 4 comments
Owner

Originally created by @pankajazad on GitHub (Jan 11, 2019).

  • Gitea version (or commit ref):
  • Git version:
  • Operating system:
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

Currently I have to define labels for each repository separately even if they have some commonality. It would be great to have a feature to define a superset of the issue labels and then make selection from them for each repository. One more possibility could be, to have export and import facility for issue labels to facilitate their inclusion across different repositories.
...

Screenshots

Originally created by @pankajazad on GitHub (Jan 11, 2019). <!-- 1. Please speak English, this is the language all of us can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/NsatcWJ) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): - Git version: - Operating system: - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: ## Description Currently I have to define labels for each repository separately even if they have some commonality. It would be great to have a feature to define a superset of the issue labels and then make selection from them for each repository. One more possibility could be, to have export and import facility for issue labels to facilitate their inclusion across different repositories. ... ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** -->
GiteaMirror added the type/feature label 2025-11-02 04:46:12 -06:00
Author
Owner

@apricote commented on GitHub (Jan 11, 2019):

It is already possible to create a file containing a set of initial labels for new repos.
This is not the solution that you and I would prefer, but it might help you in the meantime:

https://docs.gitea.io/en-us/customizing-gitea/#customizing-gitignores-labels-licenses-locales-and-readmes

@apricote commented on GitHub (Jan 11, 2019): It is already possible to create a file containing a set of initial labels for new repos. This is not the solution that you and I would prefer, but it might help you in the meantime: https://docs.gitea.io/en-us/customizing-gitea/#customizing-gitignores-labels-licenses-locales-and-readmes
Author
Owner

@pankajazad commented on GitHub (Jan 13, 2019):

Thanks for pointing out the currently available feature. It would be really helpful if you could provide an sample file to put in custom/options.

@pankajazad commented on GitHub (Jan 13, 2019): Thanks for pointing out the currently available feature. It would be really helpful if you could provide an sample file to put in custom/options.
Author
Owner

@apricote commented on GitHub (Jan 13, 2019):

There is a default file in the repository, you can find it here: https://github.com/go-gitea/gitea/blob/master/options/label/Default

@apricote commented on GitHub (Jan 13, 2019): There is a default file in the repository, you can find it here: https://github.com/go-gitea/gitea/blob/master/options/label/Default
Author
Owner

@pankajazad commented on GitHub (Jan 13, 2019):

Thanks a lot.

@pankajazad commented on GitHub (Jan 13, 2019): Thanks a lot.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#2737