Troubleshoot GitHub repositories or branches not appearing in Astro

Use this page if you are connecting GitHub to Astro and experience any of the following:

• Your GitHub organization appears, but the repository list is empty.
• Your repositories appear, but the branch list is empty.
• Mapping a branch to a Deployment fails.
• Creating a new repository from Astro fails.

These issues can occur when GitHub does not authorize Astro’s request, even if the Astro GitHub App has the correct repository permissions.

Work through the following causes in order.

Note: Authorization is per user. If another user successfully connected a repository, your GitHub account must still complete its own authorization.

Cause 1: your GitHub organization enforces SAML single sign on

If your organization requires SAML SSO, your token must be explicitly granted access to that organization before GitHub will answer requests about it.

1. Go to https://github.com/orgs/YOUR-ORGANIZATION/sso and complete the SSO prompt. This starts an active SAML session.
2. Go to your GitHub app authorizations, find Astro, and revoke it.
3. In Astro, go to Workspace Settings > Git Deploys and click Authorize GitHub Application.
4. On the GitHub consent screen, find Organization access and click Grant next to your organization, then complete the authorization.

Step 4 is important. GitHub can complete the authorization without granting access to the organization, which can result in an empty repository or branch list.

If Grant is unavailable, your organization might require an owner to approve third-party applications. Ask a GitHub organization owner to approve Astro under Organization Settings > Third-party Access, then repeat the steps above.

Cause 2: your GitHub organization has an IP allow list

If your GitHub organization restricts access by IP address, Astronomer requests may be blocked from reaching your repositories.

Resolve Astronomer’s current control plane egress addresses and add all returned IPs to your GitHub allow list under Organization Settings > Authentication security:

dig +short egress.astronomer.io

Always resolve the hostname rather than using a previously saved IP list, as the egress addresses may change.

Determine which cause applies

Ask your GitHub organization administrator whether:

• SAML SSO is enforced.
• An IP allow list is configured.

If you’re unsure, start with the SAML SSO steps.

If neither resolves the issue, contact Astronomer support  with your GitHub organization name and the approximate time of your most recent attempt.

If possible, open your browser’s Network tab, retry the operation, find the request ending in /repositories or /branches, and provide the x-request-id response header. This helps Astronomer support locate the corresponding request in the logs.

A different problem: deploys fail after the repository is connected

If the repository connects successfully but deploys fail, the Astro GitHub App might not have access to that specific repository. This is separate from your user authorization.

In your organization’s installed GitHub Apps, open Astro and confirm that the repository is included under Repository access.

If Only select repositories was selected when the app was installed, repositories created later are not automatically granted access.