GitHub Issues
Fix GitHub App install loops on company-managed accounts, missing organizations and repos, failed webhooks, permission errors, and branch mismatches.
Most GitHub integration problems trace to permissions, webhook failures, or branch mismatches.
Organization Not Showing During Setup
The starter docs flow lists your GitHub organizations. Pick one to hold the new repository. The list comes from GitHub's OAuth API. GitHub hides an organization 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.
Approve Jamdesk right away:
- 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
Members (not owners) see a Request button instead. It sends an approval request to your org admins.
Send your admins an approval request:
- 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.
Pick your personal account during setup to skip admin approval. Transfer the repo to your org afterward:
- Complete the Jamdesk setup using your personal account
- Go to the created repository on GitHub
- Open 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. We can preserve your configuration.
This doesn't work if your company manages your GitHub account. See company-managed GitHub accounts instead.
Company-Managed GitHub Accounts
GitHub blocks app installs on a company-managed account (GitHub calls these Enterprise Managed Users, or EMU). Only an organization can install apps. Without an organization, clicking Install on GitHub sends you back to the Jamdesk app page. Jamdesk signup shows "Your organization manages this GitHub account".
Managed usernames end in an underscore and a company code, like jsmith_acme. GitHub explains the limits on its page about managed user accounts.
Fix it with one of these options.
- Ask an enterprise owner to create an organization from the Organizations tab of your enterprise. Ask them to let you create repos in it.
- Transfer your docs repo into it. In the repo, go to Settings, click Transfer at the bottom, and pick the new organization.
- In Jamdesk, click Connect an existing repository (or Install GitHub App in project settings). On GitHub, pick the organization, choose Only select repositories, select your repo, and install.
If GitHub shows Request instead of Install, an organization owner gets an email to approve it. Click the Jamdesk button again after they do.
Use this when your company can't add an organization. Check with your GitHub admin first. The docs will live outside your company's GitHub.
- In a private browser window, sign in to GitHub with a personal account (or create one).
- Create an empty private repo on that account.
- Push a copy of your docs to it. GitHub can't transfer repos out of a managed enterprise.
git remote set-url origin https://jsmith@github.com/jsmith/product-docs.git
git push -u origin mainKeep jsmith@ in the URL so Git asks for your personal account's login.
- In Jamdesk, click Connect an existing repository (or Install GitHub App in project settings), install Jamdesk on your personal account, and pick the repo.
Managed accounts can't push to repos outside your enterprise. Every docs editor needs a personal GitHub account. Add them to the repo as collaborators.
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
- Open Settings → Webhooks
- Find the Jamdesk webhook
- Check "Recent Deliveries" for errors
Builds only trigger on your configured branch. Check Settings in Jamdesk.
If the build shows as failed with a message that the person who pushed isn't a member, invite them in Project Settings → Members or have them link their GitHub account. See Builds aren't triggering.
- 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
- Open 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.
