coollabsio
[Bug]: Webhook Configuration on Github link points to invalid resource
Error Message and Logs
This button links to a page that regular Coolify users cannot access: https://github.com/coollabsio/coolify/settings/hooks
Steps to Reproduce
- Create a Project
- Add a Public Repository Resource (or any resource that gives you Webhook configuration)
- Click Webhook under Configuration
- Click the "Webhook Configuration on Github" button
Example Repository URL
No response
Coolify Version
v4.0.0-beta.452
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
Ubuntu 24.04
Additional Information
I would have expected a documentation resource, not attempting to view Coolify's webhooks :)
📝 CodeRabbit Plan Mode
Generate an implementation plan and agent prompts for this issue.
- [ ] Create Plan
🔗 Similar & Duplicate Issues
Related Issues
- coollabsio/coolify#7483
- coollabsio/coolify#6799
- coollabsio/coolify#6213
- coollabsio/coolify#6319
- coollabsio/coolify#6874
- coollabsio/coolify#5626
👤 Suggested Assignees
- javimosch
- scammo
- darklight9811
- alsib
- Noriller
🧪 Issue enrichment is currently in early access.
To disable automatic issue enrichment, add the following to your .coderabbit.yaml:
issue_enrichment:
auto_enrich:
enabled: false
![coderabbitai[bot] avatar](https://avatars.githubusercontent.com/in/347564?v=4 "Published by a pub.dev verified publisher"){kind=small}
The button takes you to https://github.com/coollabsio/coolify/settings/hooks because you have entered Coolify's repository https://github.com/coollabsio/coolify as the repository url when you created the resource.
Some users have their repository public and use the "Public Repository" to deploy their app since they have access to the repository that button works without any issue.
This is not a bug but a bad UX, we probably have to hide that button for public repository based deployment to avoid confusion like this.
Interesting, and it makes me realize that I also may have misreported, this isn't from a Public Repository, but the container is from a Dockerfile... so the webhook is using a default, but not one I provided. Should I edit the original issue, or leave the correction only via this comment?
Interesting, and it makes me realize that I also may have misreported, this isn't from a Public Repository, but the container is from a Dockerfile... so the webhook is using a default, but not one I provided. Should I edit the original issue, or leave the correction only via this comment?
Yeah this section should not show for Dockerfile, Docker image and Docker compose empty deployment types