Jamdesk Documentation logo

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

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:

  1. Click grant Jamdesk access on GitHub under the organization picker (or go to GitHub → Settings → Applications → Authorized OAuth Apps → Jamdesk)
  2. Under Organization access, click Grant next to your organization
  3. 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:

  1. Go to GitHub → Settings → Applications → Authorized OAuth Apps → Jamdesk
  2. Under Organization access, click Request next to your organization. This notifies your org admins
  3. An admin approves it in the org's Settings → Third-party access → OAuth application policy (pending requests show an Approve button)
  4. 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:

  1. Complete the Jamdesk setup using your personal account
  2. Go to the created repository on GitHub
  3. Navigate to Settings → General → Danger Zone
  4. Click Transfer and select your organization as the destination
  5. 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.

This doesn't work if your company manages your GitHub account. See company-managed GitHub accounts instead.

Company-Managed GitHub Accounts

If your company manages your GitHub account (GitHub calls these Enterprise Managed Users, or EMU), GitHub won't let you install apps on your own account, only on an organization. If there's no organization for you to use, clicking Install on GitHub just sends you back to the Jamdesk app page. During signup, Jamdesk 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.

You can fix this in one of two ways.

  1. Ask an enterprise owner to create an organization from the Organizations tab of your enterprise. Ask them to let you create repos in it.
  2. Transfer your docs repo into it. In the repo, go to Settings, click Transfer at the bottom, and pick the new organization.
  3. 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 if your company can't add an organization. Check with your GitHub admin first, since the docs will live outside your company's GitHub.

  1. In a private browser window, sign in to GitHub with a personal account (or create one).
  2. Create an empty private repo on that account.
  3. Push a copy of your docs to it. GitHub can't transfer repos out of a managed enterprise, so a copy is needed.
git remote set-url origin https://jsmith@github.com/jsmith/product-docs.git
git push -u origin main

Keep jsmith@ in the URL so Git asks for your personal account's login.

  1. 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, so everyone who edits the docs needs a personal GitHub account. Add them to the repo as collaborators.

Repository Not Appearing

If your repository doesn't show in the list:

  1. Go to GitHub → Settings → Applications → Jamdesk
  2. Verify the repository has access granted
  3. Click Configure to add more repositories

For organization repos:

  1. An org admin must approve Jamdesk
  2. Go to org settings → Third-party access
  3. Approve Jamdesk's access request

Private repos require GitHub authorization. Re-authorize Jamdesk if needed.

Builds Not Triggering

If pushes don't trigger builds:

1
Check the webhook
  1. Go to your repo on GitHub
  2. Navigate to Settings → Webhooks
  3. Find the Jamdesk webhook
  4. Check "Recent Deliveries" for errors
2
Verify the branch

Builds only trigger on your configured branch. Check Settings in Jamdesk.

3
Re-sync the connection
  1. Go to project Settings in Jamdesk
  2. 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:

  1. Go to your GitHub account settings
  2. Navigate to Applications → Authorized OAuth Apps
  3. Revoke Jamdesk
  4. 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.

Still Having Issues?

Contact Support

Include your repository URL and error messages

Error Reference

Full error code list

Contact Support

Escalate unresolved issues