Troubleshooting GitHub Import Issues
Common questions and solutions when importing public GitHub repositories.
1. "Repository Not Found" or HTTP 404 Error
Symptoms
Entering a GitHub repository URL produces an error stating the repository cannot be found.
Cause
- Private Repository: Rekhic currently supports public repositories only. If the repository is private or requires authentication, GitHub returns an HTTP 404 to protect repository existence.
- Typo in URL: Ensure the URL matches the canonical format
https://github.com/owner/repository. URLs pointing to sub-folders (e.g.github.com/owner/repo/tree/main/subfolder) should be simplified to the root repository URL.
Solution
- Verify that you can view the repository in an Incognito / Private browser window without logging into GitHub.
- If the repository is private, download the project files and import them using Code to Diagram instead.
2. "GitHub API Rate Limit Exceeded" or HTTP 403
Symptoms
The repository analyzer fails with an error indicating that GitHub's rate limit was exceeded.
Cause
GitHub enforces an unauthenticated REST API limit of 60 requests per hour per IP address. If your network (or office VPN) has made multiple API calls in a short window, GitHub temporarily pauses requests until the hour window resets.
Solution
- Wait for the hourly window to reset (typically within 15–45 minutes).
- Alternatively, clone or download the repository ZIP and analyze it locally with Code to Diagram, which has no rate limits since it runs 100% locally on your machine.
3. Minimal Repositories (e.g. Hello-World)
Symptoms
Importing a repository with only a single README file produces a fallback starter diagram.
Explanation
When a repository contains no application frameworks, backend manifests, or docker configurations, Rekhic automatically creates a starter diagram featuring the project title and a README documentation node so you have an editable canvas starting point.
Next: Troubleshoot canvas rendering in Diagram Issues.