DATA OPS
BigQuery Contract Guard on Pull Request
On every dbt/SQL pull request, inspects the BigQuery tables the PR touches, flags any change that breaks a published column contract.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub pull-request webhookGitHub
- ActionFetch PR diff and resolve affected BigQuery tablesGitHub
- ActionRead live table schemas from BigQueryBigQuery
- LogicCompare live schema to committed contract; detect violations
- OutputPost blocking or passing review comment on the PRGitHub
What it does
This workflow runs as a pre-merge gate. When a pull request lands that modifies model SQL, it resolves which BigQuery tables the changed models produce, reads their live schemas, and checks them against the contracts declared in the repo. Any drop, rename, or incompatible type change is reported as a blocking comment directly on the PR.
When to use it
Use it when you want to catch contract violations at review time instead of in production. It shifts schema-drift detection left, so a reviewer sees the break before the merge button is pressed.
How it works
- 1A GitHub pull-request webhook triggers the run.
- 2Fetch the PR diff and identify the changed models and their target BigQuery tables.
- 3Read the current schema of each affected table from BigQuery.
- 4Compare live schema to the committed contract files and detect violations.
- 5If violations exist, post a blocking review comment on the GitHub PR listing each break; otherwise post an approving check.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Data Ops workflows
BigQuery Per-Team Budget Breach Alert to PagerDuty
Tracks month-to-date BigQuery scheduled-query spend per team and, when a team crosses its monthly budget, pages the team's on-call in PagerDuty and snapshots the spend breakdown…
dbt orphan model detector with Linear cleanup tickets
Scans your dbt manifest for models that no other model, exposure, or BI tool consumes.
Weekly BigQuery Cost Trend Sheet and Exec Digest
Compiles week-over-week BigQuery scheduled-query cost by owner and dataset into a Google Sheet with trend columns.
Backfill Missing Owner Labels on BigQuery Scheduled Queries
Finds scheduled queries with no owner label, infers the likely owner from creator metadata and target-table lineage, proposes a label.
Daily BigQuery Scheduled-Query Cost Attribution to Owners
Each morning, totals the prior day's on-demand bytes-billed per scheduled query, maps each query to its owner from a label, and posts a per-owner cost leaderboard to Slack.
dbt source freshness watcher with severity-routed alerts
Checks Snowflake loaded-at timestamps against each dbt source's freshness SLA, then routes warnings to Slack and hard breaches to a PagerDuty incident so stale data never…
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.