Automate sync with local rules + CI
Bowrain automates at two levels:
- Local rules, declared under the top-level
automations:key of thekapi.yamlrecipe, run on the developer's machine, for example as a pre-push check gate. - The server side covers the project's converge-on-push policy and CI pipelines.
Local rules
Declare automations: at the top level of the kapi.yaml recipe. A
pre-push check rule, for example, fires before kapi push completes, so source
reaches the server only after it passes your checks.
The server side
With bowrain.converge: on-push (the default), the server starts
a run after every push, with no workflow file. For
explicit pipelines, The loop in CI covers GitHub Actions,
GitLab CI, and the Bowrain GitHub App; the simplest GitHub workflow runs
kapi up on every push to main to process changed source on the server and
pull the results.
Every run, from a push, from CI, or started manually, lands in the project's Runs view in the web and desktop app:
The desktop app's project Automations and Runs views: automation rules that run the loop on the server on every push, and the run history (each run's state (Running, Up to date, Waiting for review), its trigger, pass count, and per-locale summary) with a Run now button to start one by hand.
Next
The full automation rule schema and event types are documented in Automation.