When creating a Issue label, should it be mutually exclusive with organization-level labels?

[seepine]

Description

I'm not sure if this is a bug. Currently, there is an organization-level label "status/reviewing", but I can still create the same repository-level label "status/reviewing". When using agent with Gitea, it's very easy to trigger the creation of duplicate labels.

Gitea Version

1.25.5-rootless

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

Git Version

No response

Operating System

No response

How are you running Gitea?

docker

Database

PostgreSQL

[wxiaoguang]

I think you mean "label" but not "tag".

And I think it's user's responsibility to manage the names, just like other system-level/org-level resources like projects, webhooks.

If you'd really like to "fix", it needs a lot of code to handle various edge cases, and will cause new unclear problems.

So, IMHO, "won't fix".

[seepine]

@wxiaoguang Hi, I was indeed talking about issue labels, but I have a different perspective on what you said.
The judgment on whether to fix it should be based on the functional design, not on "because it's too complicated.". This judgment seems to only require adding a few lines of SQL queries and checks in the repository and organization's new label addition interfaces. It doesn’t seem overly complicated.
Therefore, restricting label names from being duplicated might be a good choice.

For example, when creating a issue label on GitHub, creating the same label is not allowed.

[wxiaoguang]

For example, when creating a issue label on GitHub, creating the same label is not allowed.

Yes, it not completely "unable to do", but just very complicated.

This judgment seems to only require adding a few lines of SQL queries and checks in the repository and organization's new label addition interfaces. It doesn’t seem overly complicated.

#37192 (comment)
If you'd really like to "fix", it needs a lot of code to handle various edge cases, and will cause new unclear problems.

Creating, renaming, legacy data, label template, etc.

[seepine]

I understand your concerns. Perhaps it's a good choice to prohibit it from now on, controlling the main entry points—namely, adding new ones and renamin. Existing data remains unchanged. as it's generally rare for someone to create duplicate labels.

[lunny]

It's not a simple task. You may also need some options like allow override organization labels.