Repository navigation
TROUBLESHOOTING
Robert Trenaman edited this page Apr 28, 2026
·
1 revision
This guide covers common issues and their solutions when using GitHub Commander.
Possible Causes:
- Invalid or expired GitHub token
- Token lacks required scopes
- Network connectivity issues
Solutions:
- Verify your GitHub token is valid
- Ensure the token has required scopes (repo, workflow, delete_repo)
- Check your internet connection
- Regenerate the token if necessary
Solutions:
- Add additional scopes to your token
- Ensure you have write access to the repository
- Check organization permissions
Solutions:
- Verify the repository URL is correct
- Check your internet connection
- Ensure you have access to the repository
- Check destination folder permissions
Solutions:
- Verify your authentication
- Ensure file size is within 100 MB limit
- Check write access to repository
- Verify file path is correct
Solutions:
- Use Git LFS for large files
- Split large files into smaller chunks
- Compress files if possible
Solutions:
- Enable wiki in repository settings
- Verify file is valid Markdown
- Check authentication
- Ensure internet connection
Solutions:
- Ensure Pages is enabled for the repository
- Verify workflow file syntax
- Check that source branch exists
- Verify source directory path
Solutions:
- Check GitHub Actions logs for detailed errors
- Verify package.json or configuration
- Test build locally first
- Review framework documentation
Solutions:
- Verify registry credentials
- Check package name availability
- Validate package structure
- Ensure internet connection
Solutions:
- Use a different package name
- If you own it, update version number
- For npm, use scoped packages
Solutions:
- Verify you have changes to commit
- Resolve merge conflicts first
- Check Git configuration
Solutions:
- Add remote if missing
- Check authentication
- Pull first, then push
- Check internet connection
Solutions:
- Open conflicting files
- Look for conflict markers (<<<<<<<)
- Choose which version to keep
- Remove conflict markers
- Mark as resolved
- Commit the merge
- Check the Console: Many errors print detailed messages to the console
- Verify Permissions: Ensure you have necessary GitHub permissions
- Update Token: If operations fail, try regenerating your GitHub token
- Check Network: Ensure stable internet connection
- Clear Cache: If experiencing issues, try clearing application cache