✨ Automatic Validation for GitHub Personal Access Tokens

[Sophie235]

🚀 Feature Description

Automatically validate GitHub Personal Access Tokens (PATs) as soon as they are entered by the user. The validation should check if the token is valid and whether it has the required scopes to ensure the app functions correctly.

🎯 Purpose / Use Case

Users often paste invalid or insufficiently scoped tokens, which leads to confusing bugs or missing functionality — such as the repository selector not displaying private repositories. By validating tokens early, we can guide users before these issues arise, improving the overall user experience and reducing support load.

🛠️ Suggested Solution (Optional)

Trigger a validation request immediately after a token is entered:

• Check if the token is valid via a basic GitHub API call (e.g., /user or /repos).
• Verify the presence of required scopes (e.g., repo, read:org, etc.).
• Display a real-time success or error message near the token input field.

📎 Additional Context (Optional)

This issue is especially relevant for first-time users or when tokens expire. Similar token validation patterns are used in platforms like Vercel and Netlify to ensure smoother onboarding.

[Friedinger]

The scopes of an classic token are available in the X-OAuth-Scopes header, so in the scopes variable from github_flutter.

This is also used in Refined GitHub: https://github.com/refined-github/refined-github/blob/main/source/github-helpers/github-token.ts

But, unfortunately, this only works for classic tokens and not for fine grained ones.