-
-
Notifications
You must be signed in to change notification settings - Fork 5.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gitea action not working whenever gitea instance running under subpath #28763
Comments
reference actions/checkout#1242 |
That seems the case. However just forking action/checkout doesn't seems to fix. Service prefix even being ignored in gitea action runner. Remote gitea action not being handled properly.
|
I mean you may find someone fork |
Yes thank you. Checkout action got working with 'uses: ischanx/checkout@06c6114' |
For any ones reference: This code is responsible for ignoring subpath in action. (Search for newRemoteAction) https://gitea.com/gitea/act/src/branch/main/pkg/runner/step_action_remote.go |
There is a problem when parsing that, it's simple not easy to find out what is meant. You have a subpath as part of the uri, actions can reference a subfolder inside the repo.
Could mean both
Removing subfolder support (case 1) in Gitea Actions, would drop compat with GitHub Actions even more and allows the interpretation you want it to do. |
Agree. I am planning to remove subpath in gitea instance or make it work via redirecting in nginx. There seems no other solution. |
Automatically locked because of our CONTRIBUTING guidelines |
Description
My repo located at https://giteainstance.com/git/user/repo. Checkout action for gitea action failed with error
fatal: repository 'https:///giteainstance.com/user/repo/' not found
Gitea Version
1.21.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
No response
How are you running Gitea?
Behind nginx under subpath
Database
None
The text was updated successfully, but these errors were encountered: