-
Notifications
You must be signed in to change notification settings - Fork 9
Add Fallback Handling When Repository URL Is Not Found #37
Copy link
Copy link
Labels
area: backendRelated to Next.js API routes or Octokit/GitHub API.Related to Next.js API routes or Octokit/GitHub API.area: frontendChanges specifically for the UI/Tailwind components.Changes specifically for the UI/Tailwind components.bugSomething isn't workingSomething isn't workingdocumentationImprovements or additions to documentationImprovements or additions to documentationgood first issueGood for newcomersGood for newcomers
Metadata
Metadata
Assignees
Labels
area: backendRelated to Next.js API routes or Octokit/GitHub API.Related to Next.js API routes or Octokit/GitHub API.area: frontendChanges specifically for the UI/Tailwind components.Changes specifically for the UI/Tailwind components.bugSomething isn't workingSomething isn't workingdocumentationImprovements or additions to documentationImprovements or additions to documentationgood first issueGood for newcomersGood for newcomers
Type
Fields
Give feedbackNo fields configured for Feature.
Description
Currently, when a user pastes a repository URL into
ReadmeGenAIand the repository does not exist (invalid URL, typo, deleted repo, or private repo without access), the system does not provide a clear fallback response.We need to implement proper error handling and display a user-friendly fallback message when the repository cannot be found.
Expected Behavior
Repository not found.
Please check the URL and try again.
Example Scenario
Input:
https://github.com/user/non-existing-repo
Error / no proper feedback
Friendly fallback message displayed to the user.