Skip to main content

What is the GitHub Action integration?

The Prizm dbt Impact Analysis GitHub Action is a workflow you add to your dbt repository. When a pull request is opened or updated that changes a dbt model (.sql, .yml, or .csv), the action calls the Prizm API, evaluates the downstream lineage from every changed model, and posts a structured comment on the PR listing which Prizm-monitored assets will be affected — before the code is merged. This gives data engineers and reviewers immediate visibility into the blast radius of a model change, directly inside the GitHub pull request workflow they already use.

What this integration enables

Where this surfaces

GitHub pull requests — A Prizm impact analysis comment is posted on every PR that changes .sql, .yml, or .csv files. The comment shows:
  • Count of directly impacted assets (first-hop downstream models)
  • Count of indirectly impacted assets (multi-hop downstream models)
  • Collapsible lists of asset names with links to Prizm
The action only runs on PRs touching model files — it does not trigger on documentation, config, or non-model changes.

Use case

When a data engineer modifies models/orders.sql, they — and their reviewers — immediately see how many downstream tables, reports, and assets depend on that model before the PR is approved. This prevents unintended regressions, surfaces the need for downstream testing, and creates accountability for blast-radius awareness before merge.

Prerequisites

  • A dbt repository with GitHub Actions enabled
  • A Prizm API token (from Settings → Organization → Token)
  • A GitHub Personal Access Token (PAT) with pull request write permissions
  • The repository’s GitHub Actions default token must have read and write permissions for pull requests
  • A dbt connection configured in Prizm with lineage data for the monitored repository

Setup

Add secrets, variables, and the workflow file to your dbt repository.

Integration

What the PR comment shows, how impact is calculated, and environment mapping.