resectio commented 2022年02月02日 22:14:02 +01:00

Introduction

Currently there are two label sets: default and advanced. The advanced label set for example does not include the good first issue label since it does not fit within any category. Before implementing a messy workaround we thought about adding more label sets.

Remark

The label sets can be found at https://codeberg.org/Codeberg/gitea/src/branch/codeberg-1.16/contrib/options/label.

We will implement the new label sets on codeberg and propose our changes to upstream later since we decided to implement newer ones but we are not sure whether gitea wants them or not

# Introduction Currently there are two label sets: `default` and `advanced`. The `advanced` label set for example does not include the `good first issue` label since it does not fit within any category. Before implementing a messy workaround we thought about adding more label sets. # Remark The label sets can be found at https://codeberg.org/Codeberg/gitea/src/branch/codeberg-1.16/contrib/options/label. We will implement the new label sets on codeberg and propose our changes to upstream later since we decided to implement newer ones but we are not sure whether gitea wants them or not

resectio commented 2022年02月02日 23:35:36 +01:00

I just found an interesting label set which I created for a school project about a year ago

Prefix	Label	Description
Priority	Critical	Fix this NOW!
	High	Fix this in the next couple of days
	Medium	Fix this in the next few weeks
	Low	Fix this when you have nothing left to do
Status	Backlog	A large number of things that you should have done before and must do now
	Work in Progress	This is currently being worked on
	Review	Ready to be reviewed
	Closed	This issue or merge request is closed and will no longer be processed
Type	Bug	Something isn't working
	Documentation	Improvements or additions to documentation
	Duplicate	This issue or merge request already exists
	Enhancement	New feature or request
	Question	Further information is requested
Tag	Good first issue	Good for newcomers
	Help wanted	Extra attention is needed
	Invalid	This does not seem right
	Wontfix	This will not be worked on

I just found an interesting label set which I created for a school project about a year ago <table> <thead> <tr> <th>Prefix</th> <th>Label</th> <th>Description</th> </tr> </thead> <tbody> <tr> <td rowspan=4><b>Priority</td> <td>Critical</td> <td>Fix this NOW!</td> <tr> <td>High</td> <td>Fix this in the next couple of days</td> </tr> <tr> <td>Medium</td> <td>Fix this in the next few weeks</td> </tr> <tr> <td>Low</td> <td>Fix this when you have nothing left to do</td> </tr> </tr> <tr> <td rowspan=4><b>Status</td> <td>Backlog</td> <td>A large number of things that you should have done before and must do now</td> <tr> <td>Work in Progress</td> <td>This is currently being worked on</td> </tr> <tr> <td>Review</td> <td>Ready to be reviewed</td> </tr> <tr> <td>Closed</td> <td>This issue or merge request is closed and will no longer be processed</td> </tr> <tr> <td rowspan=5><b>Type</td> <td>Bug</td> <td>Something isn't working</td> <tr> <td>Documentation</td> <td>Improvements or additions to documentation</td> </tr> <tr> <td>Duplicate</td> <td>This issue or merge request already exists</td> </tr> <tr> <td>Enhancement</td> <td>New feature or request</td> </tr> <tr> <td>Question</td> <td>Further information is requested</td> </tr> </tr> <tr> <td rowspan=4><b>Tag</td> <td>Good first issue</td> <td>Good for newcomers</td> <tr> <td>Help wanted</td> <td>Extra attention is needed</td> </tr> <tr> <td>Invalid</td> <td>This does not seem right</td> </tr> <tr> <td>Wontfix</td> <td>This will not be worked on</td> </tr> </tr> </tbody> </table>

resectio commented 2022年02月03日 07:40:12 +01:00

Suggested from Bart Hanssens: Eclipse - RDF4J

Name	Description
bug	this issue is a bug
cannot reproduce	issue can not be reproduced (close reason)
dependencies	Pull requests that update a dependency file
duplicate	issue is a duplicate (close reason)
enhancement	issue is a new feature or improvement
epic	large issue consisting of multiple sub-tasks
good first issue	issue is a good choice for getting started as a contributor
help wanted	we could use your help in fixing this issue
internal task	a project workflow/setup task not directly impacting end users
needs documentation	Issue requires updates to the project documentation
not backwards compatible	A change that breaks backwards compatibility and needs a major release
stable	issue has gone stale (close reason)
tech debt	code refactoring, deprecation, and other technical debt tasks
website/documentation	Website update / Documentation issue
won't fix	issue won't be fixed (close reason)

Suggested from [Bart Hanssens](https://twitter.com/BartHanssens/status/1489010004183113732): [Eclipse - RDF4J](https://github.com/eclipse/rdf4j/labels) | Name | Description | |:-------------------------|:-----------------------------------------------------------------------| | bug | this issue is a bug | | cannot reproduce | issue can not be reproduced (close reason) | | dependencies | Pull requests that update a dependency file | | duplicate | issue is a duplicate (close reason) | | enhancement | issue is a new feature or improvement | | epic | large issue consisting of multiple sub-tasks | | good first issue | issue is a good choice for getting started as a contributor | | help wanted | we could use your help in fixing this issue | | internal task | a project workflow/setup task not directly impacting end users | | needs documentation | Issue requires updates to the project documentation | | not backwards compatible | A change that breaks backwards compatibility and needs a major release | | stable | issue has gone stale (close reason) | | tech debt | code refactoring, deprecation, and other technical debt tasks | | website/documentation | Website update / Documentation issue | | won't fix | issue won't be fixed (close reason) |

resectio commented 2022年02月03日 18:53:59 +01:00

Proposed the idea of modular issue sets to upstream: https://github.com/go-gitea/gitea/issues/18583

Proposed the idea of modular issue sets to upstream: https://github.com/go-gitea/gitea/issues/18583

circlebuilder commented 2022年07月18日 12:33:30 +02:00

On HN I found this page https://contrib.design/

A proposal for using contrib-design as a tag for GitHub issues, GitLab issues, forum threads, [Hey, you're missing Gitea] etc. for soliciting design contributions on open source projects.

On [HN](https://news.ycombinator.com/item?id=32135822) I found this page https://contrib.design/ > A proposal for using `contrib-design` as a tag for GitHub issues, GitLab issues, forum threads, [Hey, you're missing Gitea] etc. for soliciting design contributions on open source projects.

ncc1988 commented 2024年01月18日 18:09:33 +01:00

What about letting users define the label set in their profile?

For example, I have two projects that have all the labels I need and that do not fit into the two label sets. If I could define my own label set in the profile or pick the label set of one of my projects in another, I wouldn't have to recreate the label set for every new project that needs these labels.

What about letting users define the label set in their profile? For example, I have two projects that have all the labels I need and that do not fit into the two label sets. If I could define my own label set in the profile or pick the label set of one of my projects in another, I wouldn't have to recreate the label set for every new project that needs these labels.

circlebuilder commented 2024年01月19日 15:37:31 +01:00

A page suggesting a very nice label set: https://seantrane.com/posts/logical-colorful-github-labels-18230/

A page suggesting a very nice label set: https://seantrane.com/posts/logical-colorful-github-labels-18230/

harald commented 2024年07月18日 11:23:36 +02:00

How about copying labels

• from a users own projects only or
• from any project
• with a tick-list which labels to actually copy

Some predefined label sets are nice as an inspiration, but I can hardly imagine any team which does not have its own deeply bike-shedded deviations they swear on. And they want these on all their projects, of course, easy to copy from either a profile or another project.

Creating a template project first would require foresight nobody actually has. :-)

How about copying labels - from a users own projects only or - from any project - with a tick-list which labels to actually copy Some predefined label sets are nice as an inspiration, but I can hardly imagine any team which does not have its own deeply bike-shedded deviations they swear on. And they want these on all their projects, of course, easy to copy from either a profile or another project. Creating a template project first would require foresight nobody actually has. :-)

lars_uffmann commented 2024年09月27日 23:14:48 +02:00

Seconded. I, too, would very much appreciate being able to create my own custom label sets that I can apply to all my projects, as opposed to having to manually edit them per project.

Seconded. I, too, would very much appreciate being able to create my own custom label *sets* that I can apply to all my projects, as opposed to having to manually edit them per project.

soulstenance commented 2025年05月29日 03:20:09 +02:00

Defining custom label sets to deploy quickly across a user's repos would be brilliant. I understand the desire for a standard to base off of but sometimes I don't like the wording of a particular label, or simply don't need some. Manually editing or removing these labels can be tedious.

Defining custom label sets to deploy quickly across a user's repos would be brilliant. I understand the desire for a standard to base off of but sometimes I don't like the wording of a particular label, or simply don't need some. Manually editing or removing these labels can be tedious.

lars_uffmann commented 2025年06月18日 14:08:52 +02:00

Aaand I am also still waiting :) Here's hoping this ticket will eventually get a response / an assignee

Aaand I am also still waiting :) Here's hoping this ticket will eventually get a response / an assignee

ernest314 commented 2025年08月20日 18:25:29 +02:00

This is a feature that's been requested for years on GitHub, and creating different templates is a much better way of doing it than GitHub does.

see discussion (with lots of requests/interest): https://github.com/isaacs/github/issues/281

since that discussion was archived, here is a (more) current one: https://github.com/orgs/community/discussions/10374

This is a feature that's been requested for years on GitHub, and creating different templates is a much better way of doing it than GitHub does. see discussion (with lots of requests/interest): https://github.com/isaacs/github/issues/281 since that discussion was archived, here is a (more) current one: https://github.com/orgs/community/discussions/10374