Organization and Repository level access token

### Feature Description It would be nice to have a more limited access token than user access token. * A Repository-level access token should only be able to read/write its repository, call `/repos/` API endpoints and configure repository webhooks. * An Organization-level access token should be able to authenticate to `/orgs/` endpoints and do the same things as Repository-level access token for all the repositories inside it. I'm a long time GitLab user, so this is just my way of wanting its feature in Gitea. Also, Repository and Organization access token should also have configurable scopes at creation time. Ref: https://docs.gitlab.com/ee/security/token_overview.html ### Screenshots _No response_

Comments (0)

No comments yet. Start the discussion.

Organization and Repository level access token

Tags

Related issues

struct's lifetime requirements can be bypassed via covariant field assignment

Proposal to Reorganize the Moderation Team and Review Moderation Policies

Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss

proposal: container/...: generic collection types

Better Custom Endpoint BYOK

A concrete policy for backward compatibility until Godot 5.0

New MTP models not supported

Tracking: 429 / Capacity Issues

Organization and Repository level access token

Comments (0)