Similar to #18374 I'd like to see the same for access tokens. When I add a new access token, I'd like to be able to choose which repositories it is allowed to access, and preferably, whether the token should have read-only or read-write access to each repository.
I'd love to see the following options available for newly created access tokens:
Token is valid for:
All repositories the user can access
Select specific repositories
Token allows:
Pull only access
Pull and push access
If it makes the implementation easier, it would also be totally acceptable to have the tokens created on the repository itself instead of per user, similarly to Deploy Keys. So a user can create a personal access token for a specific repository.
There are places where I put tokens, unencrypted, because they need to push to a single repo on my gitea install. In that situation, I have to create new users to be able to limit the token to only be valid for a single repository. It would be great if there was an easier option.
Thanks for gitea, it really makes self hosting git painless and joyful. Y'all rock. 🧡
Screenshots
GitHub has a whole host of options, which I think would be overkill for gitea.
The text was updated successfully, but these errors were encountered:
Feature Description
Similar to #18374 I'd like to see the same for access tokens. When I add a new access token, I'd like to be able to choose which repositories it is allowed to access, and preferably, whether the token should have read-only or read-write access to each repository.
I'd love to see the following options available for newly created access tokens:
If it makes the implementation easier, it would also be totally acceptable to have the tokens created on the repository itself instead of per user, similarly to Deploy Keys. So a user can create a personal access token for a specific repository.
There are places where I put tokens, unencrypted, because they need to push to a single repo on my gitea install. In that situation, I have to create new users to be able to limit the token to only be valid for a single repository. It would be great if there was an easier option.
Thanks for gitea, it really makes self hosting git painless and joyful. Y'all rock.🧡
Screenshots
GitHub has a whole host of options, which I think would be overkill for gitea.
The text was updated successfully, but these errors were encountered: