Add a token to CI runs similar to GITHUB_TOKEN #9230

New Issue

GiteaMirror · 2025-11-02T08:32:49-06:00

GiteaMirror commented

2025-11-02 08:32:49 -06:00

Originally created by @dorianim on GitHub (Jul 17, 2022).

Feature Description

It would be great if Gitea would add a token to CI runs, similar to GITHUB_TOKEN. Currently, I have to generate a personal access token to push docker containers to the integrated container registry. This is a problem for organizations, as the token belongs to one member.
If that is not possible because of the way Gitea integrates with different CI-providers, it would be nice, if it was possible to create an organization wide access token.

Originally created by @dorianim on GitHub (Jul 17, 2022). ### Feature Description It would be great if Gitea would add a token to CI runs, similar to GITHUB_TOKEN. Currently, I have to generate a personal access token to push docker containers to the integrated container registry. This is a problem for organizations, as the token belongs to one member. If that is not possible because of the way Gitea integrates with different CI-providers, it would be nice, if it was possible to create an organization wide access token.

GiteaMirror added the type/proposal type/feature labels 2025-11-02 08:32:49 -06:00

GiteaMirror closed this issue

2025-11-02 08:32:49 -06:00

GiteaMirror commented

2025-11-02 08:32:50 -06:00

@6543 commented on GitHub (Jul 17, 2022):

tldr: this is not posible because of the architecture gitea integrates with ci providers

long:
If you find a CI that is willing to integrate a function to inject a token, for the repo it got the request to run the pipeline, into the ci environment - you could have souch feature ...
... I would create a "bot" account that does handle things and reuse it acordingly ..

@6543 commented on GitHub (Jul 17, 2022): tldr: this is not posible because of the architecture gitea integrates with ci providers long: If you find a CI that is willing to integrate a function to inject a token, for the repo it got the request to run the pipeline, into the ci environment - you could have souch feature ... ... I would create a "bot" account that does handle things and reuse it acordingly ..

GiteaMirror commented

2025-11-02 08:32:50 -06:00

@dorianim commented on GitHub (Jul 17, 2022):

this is not posible because of the architecture gitea integrates with ci providers

Alright, that makes sense.

this is not posible because of the architecture gitea integrates with ci providers

I feel like this is quite a hustle for such a small thing. Wouldn't it be possible to just create an access token which only works for a certain organization?

@dorianim commented on GitHub (Jul 17, 2022): > this is not posible because of the architecture gitea integrates with ci providers Alright, that makes sense. > this is not posible because of the architecture gitea integrates with ci providers I feel like this is quite a hustle for such a small thing. Wouldn't it be possible to just create an access token which only works for a certain organization?

GiteaMirror commented

2025-11-02 08:32:51 -06:00

@6543 commented on GitHub (Jul 17, 2022):

well yes with a dedicated account ... - limiting the scope of tokens is already a open feature request

@6543 commented on GitHub (Jul 17, 2022): well yes with a dedicated account ... - limiting the scope of tokens is already a open feature request

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#9230