-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Use the "clone_url" provided in the webhook response #3124
Comments
Please feel free to propose a PR |
I just did: #3124 |
Please fill out the full issue template like the drawbacks. The purpose of this check, according to the comments, is to ensure "the clone url is the same as the repo to avoid something malicious".
Let's take a step back.
|
Hi @nitrocode Thanks for the feedback. I like the idea of taking a step back. That's why I didn't propose a PR at the begining. I am using Gitbucket as VCS. This is actually the same as Github with regards to webhooks and lot more. My issue in this case is the Webhook Call Response returns "/git/my_home_folder/myrepository.git" as "clone_url". The repository full name is "my_home/myrepository". What happens then is that the expected clone_url is then computed to "my_home/myrepository.git". This check fails since the real clone_url is "/git/my_home_folder/myrepository.git". A similar issue has been described here: #1450 Does it help? Regards |
I have now looked a bit deeper into the source code. What I intend to do wouldn't work at all, since there seems to be strong ties to the pre-defined vcs repos |
Community Note
Describe the user story
As a developer, I often want to use the "clone_url" provided in the webhook response. However, based on the different kinds of installations, the base path can be different.
Describe the solution you'd like
I would like to entirely remove the check for the clone_url here:
Describe the drawbacks of your solution
Describe alternatives you've considered
The text was updated successfully, but these errors were encountered: