GitHub Issues
Fix missing repos, failed webhooks, permission errors, and branch mismatches with the Jamdesk GitHub integration.
Most GitHub integration problems trace to permissions, webhook failures, or branch mismatches.
Repository Not Appearing
If your repository doesn't show in the list:
- Go to GitHub → Settings → Applications → Jamdesk
- Verify the repository has access granted
- Click Configure to add more repositories
For organization repos:
- An org admin must approve Jamdesk
- Go to org settings → Third-party access
- Approve Jamdesk's access request
Private repos require GitHub authorization. Re-authorize Jamdesk if needed.
Builds Not Triggering
If pushes don't trigger builds:
- Go to your repo on GitHub
- Navigate to Settings → Webhooks
- Find the Jamdesk webhook
- Check "Recent Deliveries" for errors
Builds only trigger on your configured branch. Check Settings in Jamdesk.
- Go to project Settings in Jamdesk
- Click Re-sync GitHub
Webhook Errors
404 Not Found
The webhook endpoint couldn't be reached.
Fix: Re-sync the GitHub connection in project settings.
401 Unauthorized
Authentication failed.
Fix:
- Go to your GitHub account settings
- Navigate to Applications → Authorized OAuth Apps
- Revoke Jamdesk
- Re-authorize in Jamdesk settings
500 Server Error
Temporary Jamdesk issue.
Fix: Wait a few minutes and push again, or trigger a manual rebuild.
Permission Errors
"Repository not found" during build:
- The repository may have been deleted or renamed
- Jamdesk may have lost access
- Re-authorize your GitHub connection
Branch Issues
Wrong branch building
Check your configured branch in Settings → Repository.
Branch renamed or deleted
Update your branch setting to match the new branch name.