lrok

// use case

Receive GitHub webhooks on your laptop

GitHub webhooks fire on every push, PR, and issue. Testing your handler means either deploying every change or tunneling. lrok keeps the same public URL across days so the GitHub webhook config stays put.

  1. Reserve a name

    $ lrok reserve gh-hooks

  2. Run your server

    $ go run ./cmd/webhook-handler

  3. Tunnel + paste into GitHub

    Repo → Settings → Webhooks → Add webhook. Payload URL: https://gh-hooks.lrok.io/event

    $ lrok http 8080 --hint gh-hooks

  4. Inspector replays any past delivery

    GitHub redelivers cost a click in their UI. Lrok's replay button is faster — fires the captured request against your handler again with the original body.

// why lrok for this

GitHub validates webhooks via HMAC-SHA256 — for that the request body must be byte-identical. lrok proxies bytes verbatim with no rewriting, so signature checks pass.

Start freeInstall the CLISee pricing

Related workflows