Open thomas-maurice opened 1 year ago
I understand. However, permissions
doen't not work on Gitea Actions yet. See https://docs.gitea.io/en-us/usage/actions/comparison/#permissions-and-jobsjob_idpermissions
Therefore, the job can only access the related repository and not other private repositories.
Oooooh, it makes sense @wolfogre thank you! I wasn't sure if it was a bug or because the feature is still in early days. Thank you for clarifying !
And a proposal for this:
Thank you for following up :)
Description
It does not seem to be possible to use an action hosted on a private gitea instance (the runner being registered on the said instance, and the user owning both repos), the runner fails in the setup phase with:
The sample
.gitea/workflows/pr.yml
I used wasAs you see I tried to add a bunch of permissions but it didn't seem to do anything (I was working under the assumption these would work the same as github, might be wrong)
I also tried to put an
ssh://
cloning scheme but it failed as well withGitea Version
1.19.3
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
2.34.1
Operating System
Ubuntu 22.04
How are you running Gitea?
Stock binary downloaded from github
Database
PostgreSQL