github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-11 17:46:29 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Fine grained access tokens #9478

New Issue
Closed
opened 2025-11-02 08:40:04 -06:00 by GiteaMirror · 7 comments
GiteaMirror commented 2025-11-02 08:40:04 -06:00
Owner
Copy Link

Originally created by @BaseCrusher on GitHub (Aug 28, 2022).

Feature Description

I believe it would be a good feature if users could fine grain their access tokens. This would make it possible to limit what is possible with a specific token and introduce an additional layer of security.
Especially now that we have more features within gitea than just git management this would be a very neet addition.

Screenshots

No response

Originally created by @BaseCrusher on GitHub (Aug 28, 2022). ### Feature Description I believe it would be a good feature if users could fine grain their access tokens. This would make it possible to limit what is possible with a specific token and introduce an additional layer of security. Especially now that we have more features within gitea than just git management this would be a very neet addition. ### Screenshots _No response_
GiteaMirror added the type/proposaltype/feature labels 2025-11-02 08:40:04 -06:00
GiteaMirror commented 2025-11-02 08:40:06 -06:00
Author
Owner
Copy Link

@KN4CK3R commented on GitHub (Aug 28, 2022):

Duplicate of #8960

@KN4CK3R commented on GitHub (Aug 28, 2022): Duplicate of #8960
GiteaMirror commented 2025-11-02 08:40:06 -06:00
Author
Owner
Copy Link

@BaseCrusher commented on GitHub (Aug 28, 2022):

Yes but I would suggest to either make the other issue more specific or to keep this one.
Thinks like what packages registries can a token be used for and what action can be used with an token. So it's not only for read only access.

If you think this is being stated in https://github.com/go-gitea/gitea/issues/8960 then feel free to close this issue.

@BaseCrusher commented on GitHub (Aug 28, 2022): Yes but I would suggest to either make the other issue more specific or to keep this one. Thinks like what packages registries can a token be used for and what action can be used with an token. So it's not only for read only access. If you think this is being stated in https://github.com/go-gitea/gitea/issues/8960 then feel free to close this issue.
GiteaMirror commented 2025-11-02 08:40:07 -06:00
Author
Owner
Copy Link

@KN4CK3R commented on GitHub (Aug 28, 2022):

No everything fine. Just wanted to link the other issue.

@KN4CK3R commented on GitHub (Aug 28, 2022): No everything fine. Just wanted to link the other issue.
GiteaMirror commented 2025-11-02 08:40:07 -06:00
Author
Owner
Copy Link

@TheDom42 commented on GitHub (Jan 2, 2023):

As the issue described by me was out of scope for the issue described in this thread, it has now been moved to #22330

@TheDom42 commented on GitHub (Jan 2, 2023): As the issue described by me was out of scope for the issue described in this thread, it has now been moved to #22330
GiteaMirror commented 2025-11-02 08:40:07 -06:00
Author
Owner
Copy Link

@KN4CK3R commented on GitHub (Jan 3, 2023):

@TheDom42 What you are describing is totally different than what this issue is about.

@KN4CK3R commented on GitHub (Jan 3, 2023): @TheDom42 What you are describing is totally different than what this issue is about.
GiteaMirror commented 2025-11-02 08:40:08 -06:00
Author
Owner
Copy Link

@TheDom42 commented on GitHub (Jan 3, 2023):

Sorry, I must have completely misinterpreted the term "Fine grained access token". I thought this was specifically referring to the Github feature and thought that this issue was maybe about the fact that they are not yet supported by Gitea. I will move the described problem to a new one.

@TheDom42 commented on GitHub (Jan 3, 2023): Sorry, I must have completely misinterpreted the term "Fine grained access token". I thought this was specifically referring to the Github feature and thought that this issue was maybe about the fact that they are not yet supported by Gitea. I will move the described problem to a new one.
GiteaMirror commented 2025-11-02 08:40:08 -06:00
Author
Owner
Copy Link

@jolheiser commented on GitHub (Jan 20, 2023):

Resolved by #20908

@jolheiser commented on GitHub (Jan 20, 2023): Resolved by #20908
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/feature type/proposal
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#9478
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?