github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 10:39:38 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Team permission read is ignored if all permission fields are none #12183

New Issue
Closed
opened 2025-11-02 10:01:21 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-02 10:01:21 -06:00
Owner
Copy Link

Originally created by @YannMagnin on GitHub (Dec 12, 2023).

Description

When I try to change a team permission to read, the request is completely ignored if all fields of the permission map are set to none. I understand the idea behind this mechanism, but since the description of the read status is Members permissions will be decided by below permission table I'm questioning if its not a bug?

Would it be possible to explicit the read permission even if all fields are set to none ?

Gitea Version

1.21.1, 1.21.2

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

Linux Mint, EndeavourOS

How are you running Gitea?

Official binaries, and running from systemd and command-line

Database

SQLite

Originally created by @YannMagnin on GitHub (Dec 12, 2023). ### Description When I try to change a team permission to `read`, the request is completely ignored if all fields of the permission map are set to `none`. I understand the idea behind this mechanism, but since the description of the `read` status is `Members permissions will be decided by below permission table` I'm questioning if its not a bug? Would it be possible to explicit the `read` permission even if all fields are set to `none` ? ### Gitea Version 1.21.1, 1.21.2 ### Can you reproduce the bug on the Gitea demo site? Yes ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System Linux Mint, EndeavourOS ### How are you running Gitea? Official binaries, and running from systemd and command-line ### Database SQLite
GiteaMirror added the issue/needs-feedbacktype/bug labels 2025-11-02 10:01:21 -06:00
GiteaMirror commented 2025-11-02 10:01:22 -06:00
Author
Owner
Copy Link

@yp05327 commented on GitHub (Mar 11, 2024):

What do you mean if all fields of the permission map are set to none, normally they should not be none. 🤔

@yp05327 commented on GitHub (Mar 11, 2024): What do you mean `if all fields of the permission map are set to none`, normally they should not be `none`. 🤔
GiteaMirror commented 2025-11-02 10:01:23 -06:00
Author
Owner
Copy Link

@GiteaBot commented on GitHub (Apr 11, 2024):

We close issues that need feedback from the author if there were no new comments for a month. 🍵

@GiteaBot commented on GitHub (Apr 11, 2024): We close issues that need feedback from the author if there were no new comments for a month. :tea:
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 issue/needs-feedback 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#12183
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?