Cascade GitHub Integration - Fork Permission Denied
Expert cannot create GitHub forks for fix requests after Cascade modified the GitHub OAuth integration. The fork operation fails with 'permission denied' even though the user authenticated. This breaks the core expert workflow.
Cascade likely removed required OAuth scopes or modified API call authorization.
Error Messages You Might See
Common Causes
- Cascade removed 'repo' scope from GitHub OAuth configuration
- Using user's GitHub token instead of app token for fork operation
- Cascade changed fork API endpoint or request payload format
- GitHub token doesn't have necessary permissions for operation
How to Fix It
Verify GitHub OAuth scopes include 'repo' for fork creation. Ensure using correct authentication method (user token vs app). Review Cascade's API call against GitHub documentation. Test fork operation with direct curl/GitHub CLI to verify permissions. Check GitHub token's granted scopes in user settings.
Real developers can help you.
You don't need to be technical. Just describe what's wrong and a verified developer will handle the rest.
Get HelpFrequently Asked Questions
What GitHub scopes are needed?
'repo' for full repository access including forks. 'public_repo' for public repos only. Use smallest scope needed.
How do I test GitHub API calls?
Use GitHub CLI (gh api) or curl with token. Verify status code and response. Test with read-only first.