Misleading error when using fine-grained GitHub token during project creation #163
Description
Description
When creating a project in Sitebuilder, using a fine-grained GitHub token instead of a classic token results in an error message appearing under the OpenAI Key field (after the user enters their OpenAI credentials). This misleads the user into thinking there is an issue with their OpenAI credentials, while the actual problem is the GitHub token type.
Observed behavior
- User starts creating a new project.
- User provides a fine-grained GitHub token instead of a classic token.
- After the user enters their OpenAI credentials, an error message appears under the OpenAI Key field.
- This suggests the OpenAI key is invalid, even though the issue is related to the GitHub token.
- In some cases, it is still possible to create the project using a fine-grained token, but problems occur later when the user tries to start or run the project.
- When the user replaces the token with a classic GitHub token, the process works correctly.
Expected behavior
- After the user enters the GitHub token, the system should validate it against the repository access.
- Any success or error message should appear directly under the GitHub Token field, not under the OpenAI key field.
- If the token lacks required permissions or is the wrong token type, the UI should clearly indicate this.
Proposed solution
- Validate the GitHub token immediately after it is entered.
- Attempt to access the specified repository to confirm permissions.
- Display validation success or error messages directly under the GitHub Token input field.
Why this matters
- The current behavior misleads users and causes unnecessary troubleshooting.
- Users may incorrectly assume their OpenAI credentials are invalid.
- Projects created with an incompatible token may later fail when attempting to start or run, creating additional confusion.
- Clear validation feedback improves usability and reduces onboarding friction.
Environment
- Feature: Project creation (Sitebuilder)
- Scenario: Using fine-grained GitHub token instead of classic token
