Connect GitHub to Secoda to track the downstream impact of dbt model changes and sync metadata updates directly into your dbt repositories. Use GitHub pull requests as a review point for changes to data models and metadata, and stay informed about the consequences of those changes through automated impact analysis.
Add to SecodaThe GitHub integration in Secoda allows teams to track the downstream impact of code changes made in their dbt projects and manage metadata updates directly from the Secoda platform. When connected to a GitHub repository tied to your dbt models, Secoda automatically scans new pull requests to determine if any changes will affect existing assets in your workspace. If any dbt model deletions or updates are detected, Secoda will surface the impact within the pull request and notify relevant owners of affected entities.
Secoda's integration with GitHub works alongside the dbt integration to provide a seamless way to manage metadata and assess the impact of changes across your data stack. While dbt handles transformations and model creation, GitHub houses the version-controlled code. When both are connected, Secoda continuously monitors for changes and runs automated lineage-based impact analyses. If a dbt model is edited or removed, Secoda will display a clear summary of how many downstream entities will be affected and highlight what they are. These changes are visible within the pull request, making it easier for data teams to prevent accidental breakage and assess the full scope of a proposed change before merging.
To connect GitHub to your workspace, go to the Integrations tab in Secoda, search for GitHub, and select it. You’ll be prompted to authenticate via OAuth and choose where to install the integration, either to a personal or organizational account. It’s recommended to select only the repositories relevant to your dbt integration. After installing, Secoda will automatically begin scanning pull requests for changes to dbt models that are connected to your workspace. The following metadata can be edited in Secoda and pushed to your dbt repo via GitHub PR: model descriptions, column descriptions, owners, and tags.
Once connected, pull requests will include a detailed summary from Secoda, outlining the total number of downstream assets impacted by any dbt model changes. You can expand the summary to explore the full list of affected resources and use filters to view impact by integration (such as Snowflake) or type (like tables or views), all within Secoda. This information helps reviewers understand the potential consequences of a change and avoid merging code that could break dashboards or models. The integration also supports drill-down views of data dependencies, with contextual lineage depth to aid decision-making.
In addition to tracking the impact of changes, the GitHub integration allows you to sync metadata changes made in Secoda back into your dbt project. When you update descriptions, tags, column-level metadata, or ownership in Secoda, you can trigger a sync to update the corresponding dbt YAML files. Secoda will automatically open a pull request in GitHub containing these changes, allowing your team to review and merge updates directly into your codebase. This ensures that your metadata remains version-controlled, aligned with your transformations, and easy to maintain over time.
Together with the dbt integration, the GitHub integration supports the creation of a complete, reliable, and version-controlled metadata layer. As code and documentation evolve, teams can trust that changes are tracked, reviewed, and safely deployed. This setup ensures that all model-level and column-level information such as descriptions, ownership, and tags, remain up to date and consistent across both the codebase and the Secoda catalog.