yeaight7/dbt-semguard
Compare dbt Semantic Layer semantics and fail on breaking changes.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| python-version | Python version used to run dbt-semguard | — | 3.12 |
| base-ref | Base git ref for YAML comparison | no | — |
| head-ref | Head git ref for YAML comparison | no | — |
| project-dir | dbt project directory | — | . |
| base-manifest | Optional base dbt semantic_manifest.json path | no | — |
| head-manifest | Optional head dbt semantic_manifest.json path | no | — |
| fail-on | Minimum severity that should fail the action. Accepted values: `breaking`, `risky`, `safe`, `none`. | — | breaking |
| pr-comment | When true, publish or update a sticky PR comment with the semguard report | — | false |
| pr-comment-mode | PR comment behavior when a previous dbt-semguard comment exists. Use `sticky` to update the existing dbt-semguard comment or `create` to always post a new comment. | — | sticky |
| github-token | GitHub token used for PR comment publishing | no | — |
| artifact-name | Name for the uploaded JSON artifact. Internal report filenames are derived from this value. | — | semguard-report |
Outputs
| name | description |
|---|---|
| highest-severity | Highest severity detected in the generated report |
| blocking | Whether the configured fail-on threshold was reached |
| breaking-count | Number of breaking changes in the report |
| risky-count | Number of risky changes in the report |
| safe-count | Number of safe changes in the report |