§ / Recipes

Worked examples.

Each recipe is a copy-paste starting point for wiring a real CI use case onto FlareDispatch — adjust the inputs and drop it into your repo. Every recipe is a typed Effect-TS run (*.run.ts); the wiring — Webhook, Action, or Schedule — is a dimension, not a category. The chips on each card show which wirings it supports, recommended first.

Event-driven recipes also surface a baseline on their page — the full GitHub Actions workflow you'd have to maintain to do the same job without FlareDispatch — so the contrast is in plain sight.

§01

Event-driven

Fires on a GitHub event (a PR push, a deploy). Wire it as Webhook (the App fires the run directly — no ci.yml) or Action (a ci.yml step), whichever fits; both post back as a Check Run. Webhook is shipped where the run's inputs come from the event itself.

§02

Wall-clock

Fires on a Cloudflare Cron Trigger — no GitHub event, no GHA minutes, no workflow file. The cron expression also goes in wrangler.jsonc triggers.crons; a GHA on: schedule step is the GHA-native alternative.