> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dqlabs.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> What the Prizm GitHub Action integration is — posts pre-merge lineage impact analysis comments on pull requests that change dbt models.

<script type="application/ld+json">
  {`{
            "@context": "https://schema.org",
            "@type": "TechArticle",
            "headline": "GitHub Action Overview",
            "description": "What the Prizm GitHub Action integration is - posts pre-merge lineage impact analysis comments on pull requests that change dbt models.",
            "url": "https://docs.dqlabs.ai/integrations/githubaction/overview",
            "publisher": {
              "@type": "Organization",
              "name": "DQLabs Inc",
              "logo": "https://media.brand.dev/332adc35-5bc4-4d2b-bf78-256aa4a5e414.svg"
            }
            }`}
</script>

## 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

| Capability                      | Description                                                                                                                |
| ------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| **Pre-merge impact visibility** | See direct and indirect downstream asset counts and lists on every PR that touches a dbt model file.                       |
| **Lineage-aware analysis**      | Impact is calculated using Prizm's full lineage graph, including multi-hop downstream dependencies.                        |
| **Automated PR comments**       | Prizm adds a comment on PR creation and updates it in place on every subsequent push — one comment per PR, always current. |
| **Asset links in the PR**       | Each listed asset links directly to its Prizm detail page for further investigation.                                       |
| **Environment mapping**         | Map a GitHub branch to a specific dbt environment in Prizm so impact is calculated using the right environment's lineage.  |

## 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

<CardGroup cols={2}>
  <Card title="Setup" icon="gear" href="/integrations/githubaction/setup">
    Add secrets, variables, and the workflow file to your dbt repository.
  </Card>

  <Card title="Integration" icon="arrows-left-right" href="/integrations/githubaction/integrations">
    What the PR comment shows, how impact is calculated, and environment mapping.
  </Card>
</CardGroup>