GitHub Limitations and Troubleshooting

Learn about the functional limitations of the GitHub connector that affect certain behaviors and outcomes. The solutions listed below are unique to the GitHub connector. If your issue applies to other connectors, check this guide for instructions.

The following are limitations or troubleshooting information:

General Data 360 Limitations
A Data Lake Object and a Data Model Object Were Created, But the Search Index and Chunking Failed
Private Repository Access (404 Errors)

Supported File Formats

See the Unstructured Data File Formats and Connectors for a list of supported file formats.

General Data 360 Limitations

Learn about Data 360’s general limitations which may create issues for this specific connector.

A Data Lake Object and a Data Model Object Were Created, But the Search Index and Chunking Failed

When you create a new GitHub connector, you can enable search indexing.

Issue

Search Index or chunks weren’t created.

Solution

Create or rebuild the search index:

From App Launcher, select Data Cloud.
Do one of the following:
If you already have a Search index, open the Search Index tab, select the Search Index you created, and click Rebuild from the dropdown menu on the right.
If you need to create a Search index, from the Search Index tab: Click New > Easy Setup, and select the corresponding Data Model Object.

Private Repository Access (404 Errors)

If your GitHub connector passes the connection test and accesses public repositories but returns 404 errors for private repositories, you may be experiencing a permissions issue with a Fine-grained Personal Access Token (tokens starting with githubpat).

Issue

By default, fine-grained tokens may not have access to all repositories. GitHub intentionally returns a 404 (Not Found) error instead of a 403 (Forbidden) error for repositories the token cannot access to prevent revealing the existence of private repositories.

Solution

Change your token settings to include the relevant private repositories:

Log in to GitHub.com and navigate to **Settings > Developer settings > Personal access tokens > **Fine-grained tokens**.
Select the token you are using for the GitHub connector.
Open the settings to edit it.
Under the Repository access section, ensure you have selected either:
1. All repositories (simplest option), OR
2. Only selected repositories (and manually add every private repository you need to sync).
Under Repository permissions, verify that Contents is set to at least Read access.

Additional Resources

Use the Monitoring Guidelines for tips on how to track your connector’s ingestion progress.