GitHub Actions with PicoClaw

Use GitHub Actions as the trigger and let PicoClaw (on your server or homelab) perform LLM work via HTTP. This keeps CI runners thin: they POST JSON; PicoClaw holds provider keys and prompt logic.

1. Webhook or API step

In your workflow, add a step that curls your PicoClaw API or custom webhook with the payload (PR title, diff summary, issue body). Use repository secrets for HMAC or bearer tokens—never embed raw LLM keys in YAML.

2. Reachability

GitHub’s cloud runners need a public URL unless you use a self-hosted runner on the same network as PicoClaw. Options: nginx + TLS, Cloudflare Tunnel, or a small VPS relay.

3. Schedules vs push

schedule: cron in Actions pairs well with nightly digests; compare with Linux cron if you prefer all automation on one Linux host.

4. Related