Open Olen opened 6 days ago
Permissions
hasn't been implemented.
Thanks for the clarification. I tried to look through some code to figure out how the action runner token was generated, and which permissions is actually gets, but my go-fu is not at a high enough level.
However, since it seems to be allowed to update PRs, it is a bit strange that it can't create a PR, since - as far as I ca see - there are only two choices. issues.read
and issues.write
, and pr review to me sounds like a "write" (but I might be wrong).
Would t be possible to allow the action runner token to get permission to create PRs?
The same question, does this mean we cannot use CI on Gitea to create a PR?
You can specify a username and token for the action to use in the tea login add
-stage.
But it would be more convenient if the action running user already have permission to do it.
Description
There seems to be a problem with the action permissions for pull-requests
I have an action with the following permissions:
And I can see that
tea
is allowed to run most required commands.I can view pull-requests and I can comment/review on pull requests
But I am not allowed to create pull requests:
If I add another login in the run with a different token, I am allowed to create a PR.
I added some trace logging which shows that this is a permission problem:
Gitea Version
1.22.3
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
git version 2.45.2
Operating System
docker
How are you running Gitea?
docker image: gitea/gitea:latest
Database
MySQL/MariaDB