If your Git provider uses an IP allowlist, make sure the Maia IP addresses for Git repositories for your region are on it. Read Requests blocked by an IP allowlist for more information.
Authorization fails
This can happen if Maia can’t connect to GitHub. If you see an authorization error, refresh the page and try again. If the issue persists, either GitHub or Maia may be experiencing an issue.Requests blocked by an IP allowlist
If your GitHub organization uses an IP allowlist that doesn’t include the Maia IP addresses, GitHub blocks Maia. Maia then can’t list your repositories, connect a repository, or perform Git actions that interact with the remote repository, such as Pull remote changes. To resolve this issue, ask a GitHub organization owner to do one of the following:- Add the Maia IP addresses for Git repositories for your region to the allowlist.
- Turn on the GitHub setting that adds the Maia app’s IP addresses for all regions. Read Organizations that use an IP allowlist.
Unable to retrieve repositories
This error can happen for a number of reasons, which you can resolve as described below.Cause 1: The Maia app isn’t installed in your organization
Make sure the Maia app is installed in the correct GitHub organization. Follow the steps at Installing the Maia app in GitHub.Cause 2: The Maia app does not have access to the repository you wish to connect
Visithttps://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 Maia 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 Maia app in GitHub.
Cause 3: The Maia 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 Maia app is installed in. The user needs at least theWrite role to the repository to use that repository with Maia.
Read Repository roles for organizations to learn more about roles in GitHub.
Cause 4: The repository does not exist
Visithttps://github.com/organizations/<your-org-name>/settings/installations and click Configure. Here you can view the list of repositories that the Maia app has access to. If no repositories are selected, create a repository in that organization first, and then create a project in Maia.
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 Maia app is installed. You need at least theWrite role to the repository to use that repository with Designer. 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 Maia. 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 Maia app in your organization, only the main branch in the repository that you sync to your Maia 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:- Log in to your GitHub Account.
-
Click Settings → Applications and then choose the Authorized GitHub Apps tab. Click Revoke next to the Maia for Github app.
Make sure the Maia for Github app is already installed.
- Log out of your GitHub account.
- Access Maia and perform a Git action that interacts with the remote repository, such as Pull remote changes.
- 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.
- For GitHub only. Once you click Authorize, the browser tab will close and return you to Maia. 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 toRead even if you previously had Write access. Because Designer needs Write access to create branches, this prevents you from creating new branches in projects connected to that repository.
To resolve this issue:
- 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.
- If your role has changed to
Read, ask an organization owner to restore yourWriterole. - Reauthorize your GitHub connection in Maia by following the steps in Permission denied to access GitHub repository.