Skip to main content
Omni supports three methods for connecting to a GitHub-hosted dbt repository:
  • GitHub App authentication - Uses a GitHub app to perform authentication. Enables commit signing.
  • SSH authentication — Uses a deploy key to connect Omni to your repository. This is the traditional method and requires configuring a deploy key in your Git provider.
  • HTTPS token authentication — Uses an access token to authenticate. This method is simpler to set up because it doesn’t require deploy keys.

​
Select an authentication method

To view instructions, select the authentication method you want to use from the dropdown menu on the right side of the page, above the table of contents.
Authentication method selection menu on right side of this page

Select your authentication method from the dropdown to view setup instructions

​
Next steps

After you successfully connect your dbt repository, you need to:
  1. Configure your production dbt environment
  2. Sync dbt with Omni
  3. Set up Virtual Schemas. This isn’t required to use the dbt integration, but enabling Virtual Schemas before you start building in Omni avoids migrating later.

​
Troubleshooting

If the connection test fails when using GitHub App authentication, verify:
  • Installation ID is correct - The installation ID must be numeric and match the Omni GitHub App installation for your repository or organization. You can find this in your GitHub settings under Integrations > GitHub Apps > Configure.
  • GitHub App is installed - The Omni GitHub App must be installed and granted access to the repository. Check your GitHub organization or repository settings to confirm.
  • Repository URL is correct - The repository URL must be an HTTPS URL starting with https://github.com/.
  • GitHub App is configured in Omni - Your Omni instance must have the GitHub App configured. If the GitHub App option doesn’t appear in the authentication method dropdown, contact your Omni administrator.
If you continue to experience issues, try using SSH or HTTPS token authentication instead.