github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-22 14:34:54 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Automated users can apply multiple labels of same type despite exclusive setting #11759

New Issue
Closed
opened 2025-11-02 09:46:59 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-02 09:46:59 -06:00
Owner
Copy Link

Originally created by @Andre601 on GitHub (Oct 1, 2023).

Description

When you use a user with some form of automation (i.e. using a dependency update software such as Renovate) can said user apply multiple labels of the same type, even if the labels in question have a exclusive setting enabled and should therefore not be applied simultaneously.

As an example, in an older PR did my automated account apply multiple labels of the PR Target type. See screenshots

Gitea Version

1.20.4+0-49-g6b44939de (Note: Forgejo version, but issue exists in gitea too)

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

(Unable to provide due to not self-hosting gitea)

Screenshots

grafik

Git Version

No response

Operating System

No response

How are you running Gitea?

Not self-hosting it. Instead using an existing host (Codeberg) for it.
The software used is forgejo, but from what I can tell is this issue not specific to it and therefore exists within gitea too.

Database

None

Originally created by @Andre601 on GitHub (Oct 1, 2023). ### Description When you use a user with some form of automation (i.e. using a dependency update software such as Renovate) can said user apply multiple labels of the same type, even if the labels in question have a `exclusive` setting enabled and should therefore not be applied simultaneously. As an example, in an older PR did my automated account apply multiple labels of the `PR Target` type. See screenshots ### Gitea Version 1.20.4+0-49-g6b44939de (Note: Forgejo version, but issue exists in gitea too) ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist (Unable to provide due to not self-hosting gitea) ### Screenshots ![grafik](https://github.com/go-gitea/gitea/assets/11576465/85857bad-b196-40a3-a232-6dfcecfb4f31) ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? Not self-hosting it. Instead using an existing host (Codeberg) for it. The software used is forgejo, but from what I can tell is this issue not specific to it and therefore exists within gitea too. ### Database None
GiteaMirror added the type/bug label 2025-11-02 09:46:59 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#11759
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?