GitHub Issues
Fix missing organizations during setup, 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.
Organization Not Showing During Setup
During the starter docs flow, Jamdesk shows your GitHub organizations so you can pick where to create the repository. The list comes from GitHub's OAuth API, and GitHub hides organizations from it in two cases:
- OAuth app restrictions: your org restricts third-party app access (GitHub's default for new organizations) and hasn't approved Jamdesk yet.
- SAML SSO: your org requires SAML authentication before the API returns it.
If you own the organization, you can approve Jamdesk immediately:
- Click grant Jamdesk access on GitHub under the organization picker (or go to GitHub → Settings → Applications → Authorized OAuth Apps → Jamdesk)
- Under Organization access, click Grant next to your organization
- Back in the Jamdesk setup flow, click refresh the list. Your organization appears right away
If you're a member (not an owner), you'll see a Request button instead; clicking it sends an approval request to your org admins.
If you're a member without owner rights, send your admins an approval request first:
- Go to GitHub → Settings → Applications → Authorized OAuth Apps → Jamdesk
- Under Organization access, click Request next to your organization. This notifies your org admins
- An admin approves it in the org's Settings → Third-party access → OAuth application policy (pending requests show an Approve button)
- Return to the Jamdesk setup flow and click refresh the list; your organization should now appear
See GitHub's guide on approving OAuth apps for your organization for detailed steps.
Don't want to wait for admin approval? Pick your personal account during setup and transfer the repo to your org afterward:
- Complete the Jamdesk setup using your personal account
- Go to the created repository on GitHub
- Navigate to Settings → General → Danger Zone
- Click Transfer and select your organization as the destination
- In Jamdesk, disconnect and reconnect the repository from your project's Settings page
Disconnecting and reconnecting generates a new docs URL (e.g., your-project.jamdesk.app may change). If you've already shared your URL or set up a custom domain, contact support before disconnecting so we can preserve your configuration.
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.