GitHub Action
Drop in examples/github-actions/vectordata-dbt-ci.yml or use action/dbt-ci after dbt build.
Product · Data CI
PR Data CI / CD
Fail the PR when dbt fails — with a Fix-first check run and calm comment, not a wall of CI logs.
The problem
Metaplane-class teams block bad data in PRs. Most lean stacks only discover broken models after merge — or drown in raw dbt CI output.
The outcome
VectorData Data CI uploads run_results.json from GitHub Actions, posts a Check Run + PR comment with Fix-first triage, and fails the job on model/test failures. Same calm grouping as production Watchdog.
PR-time
Check run + comment
Fix-first
Root-cause list
Live
GitHub Action + webhook
What you get
Check runs & PR comments
Markdown summary with health score, failed models/tests, and Fix-first — via GITHUB_TOKEN.
Same parser as production
POST /api/webhooks/dbt — one artifact path for CI and prod calm alerts.
Warehouse-agnostic dbt
Works with dbt-bigquery, dbt-snowflake, or any adapter that emits run_results.json.
- ✓Docs: /docs/integrations/github-actions-data-ci
- ✓Webhook API: /docs/api/webhooks-dbt
- ✓Example workflow in examples/github-actions/
- ✓Production triage still lives in /vectordata/dbt-failures
Related
Product · Reliability
Watchdog / Fix first
AI ranks incidents by blast radius so you fix the break that unblocks everything else.
Product · Workflows
Calm alert routing
Email, Slack, webhook — one notification per root cause.
Product · Workflows
Integrations catalog
BigQuery, dbt, Slack, and the destinations lean teams actually use.
Try VectorData, then decide
Open workspace, or book a Data Stack Health Audit credited toward Managed.