Skip to content

Troubleshooting guide for connecting a GitHub repository to the Data Productivity Cloud

This page is a list of troubleshooting guidance in the event that you experience issues when connecting your GitHub repository to a Data Productivity Cloud project. Each scenario includes both an issue and a solution.

Authorization fails

Possible cause: the Data Productivity Cloud can't reach GitHub.

Solution: If you receive an authorization error, refresh the page and try again. If the issue persists, either GitHub or the Data Productivity Cloud may be experiencing an issue.

Unable to retrieve repositories

Possible cause 1: Matillion app not installed in the user's organization.

Solution: Make sure the Matillion app is installed in the correct GitHub organization. Follow the steps at Installing the Matillion Data Productivity Cloud app in GitHub.

Possible cause 2: The Matillion app does not have access to the repository you wish to connect.

Solution: visit https://github.com/organizations/<your-org-name>/settings/installations (replace <your-org-name with the org name in your GitHub URL) and click Configure. From here you can view a list of repositories that the Matillion app has access to. Confirm that the repository you're looking for is on the list. If it isn't, follow the steps at Installing the Matillion Data Productivity Cloud app in GitHub.

Possible cause 3: The Matillion app has access to the repository but the user does not.

Solution: Make sure your GitHub user has the correct repository role in the organization that the Matillion app is installed in. The user needs at least the Write role to the repository to use that repository with the Data Productivity Cloud.

Read Repository roles for organizations to learn more about roles in GitHub.

Possible cause 4: The repository does not exist.

Solution: Visit https://github.com/organizations/<your-org-name>/settings/installations and click Configure. Here you can view the list of repositories that the Matillion app has access to. If no repositories are selected, create a repository in that organization first, and then create a project in the Data Productivity Cloud.

Users can't see data pipelines in Designer

Possible cause 1: User does not have the correct repository role in GitHub.

Solution: Make sure your GitHub user has the correct repository role in the organization where the Matillion app is installed. You need at least the Write role to the repository to use that repository with Designer. Read Repository roles for organizations to learn more.

Possible cause 2: GitHub repository does not have a default branch called main.

Solution: One of the prerequisites to connect your GitHub repository to a project in the Data Productivity Cloud is to have a default branch called main.

When you create a new repository and add a first commit, GitHub automatically creates a default branch named main. It is advised to not rename this branch.

Note

When you enable the Matillion app in your organization, only the main branch from repository that you sync to your Data Productivity Cloud project will be synced. Other branches will be ignored.

Unable to push to GitHub repository

Possible cause: User has the correct Write repository role, but they have checked the "Keep my email addresses private" and "Block command line pushes that expose my email" checkboxes.

Solution: Navigate to your profile settings at https://github.com/settings/emails and uncheck the "Block command line pushes that expose my email" checkbox.

Permission denied to access GitHub repository

Possible cause: User has clicked Continue on the GitHub SSO page instead of Authorize.

Solution: To reauthorize your GitHub connection:

  1. Log in to your GitHub Account.

  2. Click Settings → Applications and then choose the Authorized GitHub Apps tab. Click Revoke next to the Matillion for Github app.

    Note

    Make sure the Matillion for Github app is already installed.

  3. Log out of your GitHub account.

  4. Access the Data Productivity Cloud and perform a Git action that interacts with the remote repository, such as Pull remote changes.
  5. Return to GitHub, go through the authorization process until you get to the Single Sign on step. Click Authorize, and continue until this process is complete.