Skip to main content
This guide lists and explains some common error messages that you may encounter when . Where applicable, it also explains how to resolve the underlying issue. After following the steps to resolve an issue, if the error persists, raise a Support ticket. For more information about Support tickets, read Getting support. If you encounter an error that you think we should add to this guide, contact our Support team to let us know.
For basic connectivity issues, make sure the Hybrid SaaS agents and Git repositories IP addresses are allowed on your repository.

​
Authorization fails

This can happen if can’t connect to GitHub. If you see an authorization error, refresh the page and try again. If the issue persists, either GitHub or may be experiencing an issue.

​
Unable to retrieve repositories

This error can happen for a number of reasons, which you can resolve as described below.

​
Cause 1: The app isn’t installed in your organization

Make sure the app is installed in the correct GitHub organization. Follow the steps at Installing the app in GitHub.

​
Cause 2: The app does not have access to the repository you wish to connect

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 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 app in GitHub.

​
Cause 3: The app has access to the repository but your GitHub user doesn’t

Make sure your GitHub user has the correct repository role in the organization that the app is installed in. The user needs at least the Write role to the repository to use that repository with . Read Repository roles for organizations to learn more about roles in GitHub.

​
Cause 4: The repository does not exist

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

​
Cause 5: You authorized with a different user that doesn’t have access to the desired repository

Follow the instructions in Reconnecting your Git user account with the user that has access to the desired repository.

​
Unable to see pipelines in Designer

This error can happen for a number of reasons, which you can resolve as described below.

​
Cause 1: You don’t have the correct repository role in GitHub

Make sure you have the correct repository role in the organization where the app is installed. You need at least the Write role to the repository to use that repository with . Read Repository roles for organizations to learn more.

​
Cause 2: GitHub repository does not have a default branch called main

Your GitHub repository must have a default branch called main in order to connect to a project in . Make sure that the default branch in your GitHub repository is called main.
When you create a new repository and add a first commit, GitHub automatically creates a default branch named main.When you enable the app in your organization, only the main branch in the repository that you sync to your project will be synced. Other branches will be ignored.

​
Unable to push to GitHub repository

This can happen if you have selected the Keep my email addresses private and Block command line pushes that expose my email checkboxes in your GitHub settings. To resolve this issue, navigate to your GitHub Email settings at https://github.com/settings/emails, then clear the Block command line pushes that expose my email checkbox.

​
Permission denied to access GitHub repository

This can happen if you click Continue on the GitHub SSO page instead of Authorize. 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 for Github app.
    Make sure the for Github app is already installed.
  3. Log out of your GitHub account.
  4. Access 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.
  6. For GitHub only. Once you click Authorize, the browser tab will close and return you to . On successful authorization, confirm if you can see your account in the list of authorized accounts. Click Continue to close the dialog.

​
Unable to create branches after being removed and re-added to a GitHub organization

This can happen if you’re temporarily removed from a GitHub organization, for example due to a two-factor authentication issue, and then re-invited. When this happens, your repository role can be downgraded to Read even if you previously had Write access. Because needs Write access to create branches, this prevents you from creating new branches in projects connected to that repository. To resolve this issue:
  1. Log in to your GitHub account and check your repository role in the organization that owns the connected repository. Ask an organization owner to confirm this if you’re not sure.
  2. If your role has changed to Read, ask an organization owner to restore your Write role.
  3. Reauthorize your GitHub connection in by following the steps in Permission denied to access GitHub repository.