GitHub webhook fires a magic link, the magic link does the rest

GitHub sends a webhook on push. Traditional path: a server with an endpoint, a signature check, a queue, a worker that does the deploy. Four moving parts to write and maintain.

You give GitHub a hoody-curl GET URL as the webhook target. The URL wraps a POST to your container's terminal endpoint with the deploy command in the json body. GitHub fetches it on every push. hoody-curl forwards the wrapped POST. The terminal runs the build. The receipt: exit code, last 100 lines of stdout: comes back as the response body, visible in GitHub's webhook delivery log.

No app between GitHub and the container. No queue. One URL.

The webhook receiver is a URL you wrote once.