Originally created by @BLACK4585 on GitHub (Dec 13, 2025).
Currently, when you set a server to Git Repo mode, you get a Webhook URL to redeploy the updated services.
But when using a GitOps homelab system, the new repo needs to be pulled first.
My idea is to add a second webhook to pull and redeploy updated services. Just redeploying updated services in a git repo without pulling first does nothing, so the current webhook could even be replaced.
When you select "File On Disk" mode, the current webhook is fine.
Originally created by @BLACK4585 on GitHub (Dec 13, 2025).
Currently, when you set a server to Git Repo mode, you get a Webhook URL to redeploy the updated services.
But when using a GitOps homelab system, the new repo needs to be pulled first.
My idea is to add a second webhook to pull and redeploy updated services. Just redeploying updated services in a git repo without pulling first does nothing, so the current webhook could even be replaced.
When you select "File On Disk" mode, the current webhook is fine.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @BLACK4585 on GitHub (Dec 13, 2025).
Currently, when you set a server to Git Repo mode, you get a Webhook URL to redeploy the updated services.
But when using a GitOps homelab system, the new repo needs to be pulled first.
My idea is to add a second webhook to pull and redeploy updated services. Just redeploying updated services in a git repo without pulling first does nothing, so the current webhook could even be replaced.
When you select "File On Disk" mode, the current webhook is fine.