Goal
Make SchemaLock trivially adoptable as a CI step for any Wave-funded repo, without hand-rolling the install + run steps in every backend's own workflow.
Scope
- Publish a reusable composite GitHub Action (
BreachDirect/schemalock-action or an action.yml in this repo) so consumers write:
- uses: BreachDirect/schemalock@v1
with:
config: schemalock.yaml
base-url: http://localhost:8000
- PR status check integration (annotate failing endpoints as PR check annotations, not just log output).
- Slack/Discord/webhook notification on failure, configurable via CLI flag or config.
- Badge generation (pass/fail SVG badge for README).
Why
Phase 1 requires each consuming repo to install SchemaLock and wire up its own CI steps by hand (as this repo's own .github/workflows/ci.yml demonstrates). A packaged Action removes that boilerplate for every Wave backend adopting it.
Acceptance criteria
Goal
Make SchemaLock trivially adoptable as a CI step for any Wave-funded repo, without hand-rolling the install + run steps in every backend's own workflow.
Scope
BreachDirect/schemalock-actionor an action.yml in this repo) so consumers write:Why
Phase 1 requires each consuming repo to install SchemaLock and wire up its own CI steps by hand (as this repo's own
.github/workflows/ci.ymldemonstrates). A packaged Action removes that boilerplate for every Wave backend adopting it.Acceptance criteria
uses:step with no manual Python setup.