-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Error 500 when updating githooks on mirrored repositories #3696
Comments
Seconding this issue/question. I'd love to use a gitea mirror to execute git hooks on my git server host – having git hooks available would be very helpful. |
@rixx any logs? |
There aren't really any logs – while the frontend shows a large "500", the logs show a 404, which happens when gitea tries to access the non-existing hook directory (usually there is a But that's not really the point – I have manually created a (Motivation: It would be really cool if this was possible – this would allow to do stuff like continuous delivery from your own servers with very little effort for repositories you can't or won't move away from other platforms.) If I can provide more help, please tell me – unfortunately the mirror update doesn't seem to log anything to the syslog on my machine, so I can't tell you if it has any issues. Mirror updates definitely happen correctly as before. |
Can confirm that this issue appears on 1.5.2 -- both in a Docker and normal environment. Only one relevant line pops up in the log:
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions. |
Regardless, this issue still occurs. |
Can confirm I'm also getting this issue on Gitea version 1.5.3 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions. |
Regardless, this issue still occurs. |
Yep found out about the same error today. I wanted to start build jobs of another repository, using a mirrored repository since the webhooks can't send custom post parameters To bad this doesn't work either :( |
[x]
):Description
Since try.gitea.io isn't working at the time of this writing I couldn't test it. But after looking at the code the issue should exist there too.
When creating a migration, and the repository is a mirror, the code doesn't seem to create the git hook repositories that it expects to find, resulting in a file not found error. Image 1 shows a newly created repository that isn't a mirror. There we can see three folders that contain the three sample hooks that are presented in the Gitea Web GUI (Image 2). A newly created repository that is a mirror, doesn't create these folders (Image 3).
Is this intended? Is there a reason why you shouldn't be able to create git hooks for mirrored repositories?
Screenshots
Image 1
Image 2
Image 3
The text was updated successfully, but these errors were encountered: