DATA OPS
BigQuery schema-contract gate on GitHub PRs
On every pull request touching schema definitions, compares the proposed table shape against the live BigQuery schema and the declared data contract.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub pull request touches schema filesGitHub
- ActionRead live table schema from BigQueryBigQuery
- LogicDiff proposed vs. live; check contract declaration
- OutputComment verdict and set blocking commit status on GitHubGitHub
What it does
Shifts schema-drift detection left into code review. When a PR proposes changes to a BigQuery table's DDL or schema file, it diffs the proposed shape against both production and the registered data contract, and posts a verdict comment that gates the merge.
When to use it
Use it when schema changes flow through version control and you want breaking changes declared and reviewed rather than discovered in production. It turns the data contract into an enforced check instead of a wiki page.
How it works
- 1A GitHub pull-request event triggers the flow when schema files change.
- 2The flow reads the proposed schema from the PR and the current live schema from BigQuery.
- 3A logic step computes the diff and checks whether any breaking change was declared in the PR's contract annotation.
- 4If the change is purely additive or properly declared, it posts a passing status comment.
- 5If an undeclared breaking change is found, it posts a failing comment listing the offending columns and sets a blocking commit status on GitHub.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect BigQueryDatasets, queries, schemas.
- 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.