Prerequisites
- A GitHub account with admin access to the repositories you want to connect.
- At least one repository that contains dbt model code or SQL files that reference warehouse schemas.
Connection Setup
Go to Connectors, click Add Connector, and select GitHub.OAuth Authorization
Clicking Connect redirects you to GitHub where you authorize the Datawise GitHub App. During authorization you can choose:- All repositories — Datawise can access any repo in your organization.
- Selected repositories — Datawise only accesses repos you explicitly choose. Add more later from GitHub under Settings > Applications > Authorized GitHub Apps.
Selecting Repos
After authorization, select which repositories Schema Guardian should monitor.How Schema Guardian Works
When a pull request is opened or updated:- Datawise fetches the PR diff from GitHub.
- SQL and dbt model files are analyzed using AI to identify schema changes.
- Breaking changes are classified: column removals, renames, type changes, breaking model restructures.
- Downstream impact is resolved using your connected warehouse and dbt lineage.
- A bot comment is posted in the PR with breaking changes, impacted assets, and mitigation recommendations.
Merge Protection
When enabled, Datawise posts a GitHub status check alongside the bot comment. If a breaking change is detected, the check returnsfailure and blocks the merge button.
Available on: Pro and Enterprise.
To enable:
- Go to Settings > Merge Protection in Datawise.
- Toggle on the repos where you want enforcement.
- In GitHub, add
datawise/schema-guardianas a required status check in your branch protection rules.
Admin users can override a blocked merge from the Schema Guardian view in Datawise.
Permissions
After Connecting
- Schema Guardian begins analyzing new pull requests in connected repos automatically.
- The Schema Guardian view shows all analyzed PRs, detected changes, and bot comment status.
- Historical PRs are not retroactively analyzed.