Overview

With the GitHub integration, you can:

After installing the GitHub Integration, turn on what you need. See Capabilities.

The Monte Carlo GitHub App cannot push commits, create branches, or merge pull requests. It can't bypass branch protection rules, required approvals, or required status checks.

Setup

Permissions required:

• Read access to administration and metadata
• Read and write access to issues and pull requests
• Read and write access to repository checks
• Read-only access to repository contents

Write access is only used to post pull request comments and check runs, and only on repos you turn this on for. Installing the app doesn't post anything. It can't push code or merge pull requests. If you enable draft PRs from Reinforcement Loop fixes, your own workflow opens them.

To connect GitHub:

1. In Monte Carlo, go to Settings → Integrations and click Add.
2. Under Code Repositories, select GitHub.
3. In GitHub, select the organization, and optionally limit access to specific repositories.
4. Click Install and Authorize. You'll be redirected back to Monte Carlo.

If you're not a GitHub organization owner, GitHub sends an approval request to the owner. The integration appears once they approve. Repeat for each organization.

dbt integrations (optional)

A dbt integration isn't required, but connecting one lets Monte Carlo map code changes to your dbt models and assets. Pull request history on asset pages and the PR Agent's validation notebooks require it. See dbt integration setup.

dbt Cloud

Setup is automatic. On data collector versions before v14050, configure the remote location manually (see dbt Core).

dbt Core

Provide the remote location of each dbt project:

1. Go to Settings → Integrations → GitHub → (your org) → Edit connection.
2. Open the Configure dbt Projects tab.
3. For each dbt project, enter:

You can also use the GraphQL API:

mutation updateDbtProjectInfo($uuid: UUID!, $remoteUrl: String, $subdirectory: String) {
  updateDbtProjectInfo(uuid: $uuid, remoteUrl: $remoteUrl, subdirectory: $subdirectory) {
    project {
      uuid
    }
  }
}

Remote URL format: https://github.com/<org>/<repo> or git://github.com/<org>/<repo>.git.

Subdirectory: for analytics/models/foo/bar.sql, use analytics. For models/foo/bar.sql, leave it empty.

Next steps

Viewing pull requests on incidents and assets in Monte Carlo work as soon as the app is installed. Follow the steps below for additional capabilities:

To check that pull requests are coming through, look for merged pull requests on incident charts after your next merges.

Troubleshooting

Limitations

• MC only collects PRs that merged after the integration setup time. Historical PRs are not available.
• Schema change monitors do not display GitHub pull requests.
• Pull request history on the asset page requires a dbt integration.
• Organizations using IP allowlists must add Monte Carlo's SaaS public IP address (see Account Information).

FAQ

Q: I just set up the integration. Why don't I see pull requests showing up yet?

MC only collects PRs that merged after the integration setup time. It does not have access to historical PRs, so it may take a few hours or days for PRs to start appearing depending on how frequently your team merges.

Q: Why can't I see pull requests for schema change alerts?

Schema change monitors don't use machine learning or the GitHub integration. They compare table schema hour-over-hour and identify differences, so they will not show GitHub pull requests.

Q: Why can't I see pull requests in the asset summary page?

A dbt integration is required to see pull request history on the asset page.

Q: My PRs are not showing up in Monte Carlo and my GitHub organization uses an IP allowlist. Do I need to allowlist any Monte Carlo IPs?

Yes. Add Monte Carlo's SaaS public IP address to your GitHub organization's IP allowlist. You can find the IP address on the Account Information page.