You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use the new gitea actions feature with a private repo which has lfs usage.
Please note, that I use another docker image because default debian image from your default act_runner config does not have "git lfs" and "yarn" installed.
Backport #23841 by @Zettat123Close#23824
Actions cannot fetch LFS objects from private repos because we don't
check if the user is the `ActionUser`.
Co-authored-by: Zettat123 <zettat123@gmail.com>
Description
Hi,
I use the new gitea actions feature with a private repo which has lfs usage.
Please note, that I use another docker image because default debian image from your default act_runner config does not have "git lfs" and "yarn" installed.
My testing workflow:
I think using the other image should not be an issue. I am using your default
actions/checkout@v3
.Here is the log of gitea actions web ui:
I removed the first successfull lines of the log (successfully fetching) and the server url, because it is a private server.
The act runner is built today.
I did not test it on try.gitea.io, because actions is not enabled in this environment.
Thank you for your help and this great tool
Gitea Version
1.19.0
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
linux
How are you running Gitea?
Gitea runs in docker.
Database
SQLite
The text was updated successfully, but these errors were encountered: