Problem
Currently, when invalid GitHub usernames, invalid tokens, or inaccessible search requests are submitted in the Tracker page, the application displays raw GitHub API error responses directly to the user.
Example:
"Validation Failed: The listed users cannot be searched either because the users do not exist or you do not have permission to view the users."
This can be confusing and not very user-friendly for normal users.
Suggested Improvement
- Replace raw API error responses with cleaner and more understandable messages
- Differentiate between common cases such as:
- invalid username
- invalid/expired token
- permission issues
- failed API requests
- Improve error UI/feedback consistency on the Tracker page
Expected Outcome
Users should receive clear and actionable validation/error messages instead of raw GitHub API responses.
Additional Context
I tested this on the Tracker page by submitting invalid search inputs and noticed that the current error handling directly exposes raw GitHub API messages.
I would like to work on this issue under GSSoC 2026. Kindly assign it to me.
Problem
Currently, when invalid GitHub usernames, invalid tokens, or inaccessible search requests are submitted in the Tracker page, the application displays raw GitHub API error responses directly to the user.
Example:
"Validation Failed: The listed users cannot be searched either because the users do not exist or you do not have permission to view the users."
This can be confusing and not very user-friendly for normal users.
Suggested Improvement
Expected Outcome
Users should receive clear and actionable validation/error messages instead of raw GitHub API responses.
Additional Context
I tested this on the Tracker page by submitting invalid search inputs and noticed that the current error handling directly exposes raw GitHub API messages.
I would like to work on this issue under GSSoC 2026. Kindly assign it to me.