---
title: GitHub Issues
description: 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. If your org isn't in the list, it's usually one of two things:

- OAuth app restrictions: your org restricts third-party app access (GitHub's default for new organizations).
- SAML SSO: your org requires SAML authentication before the API returns it.

<Accordion title="Ask your org admin to approve Jamdesk">
  Organization admins can grant Jamdesk access:

  1. Go to your GitHub organization's **Settings**
  2. Select **Third-party access** (under Security)
  3. Find **Jamdesk** in the pending requests, or click **Grant** to approve it
  4. Return to the Jamdesk setup flow; your organization should now appear

  If you don't see a pending request, start the Jamdesk setup flow first. GitHub sends an access request to your org admins automatically when you authorize the app. See GitHub's guide on [approving OAuth apps for your organization](https://docs.github.com/en/organizations/managing-oauth-access-to-your-organizations-data/approving-oauth-apps-for-your-organization) for detailed steps.
</Accordion>

<Accordion title="Create in your personal account and transfer later">
  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

  <Warning>
    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](/help/support/contact) before disconnecting so we can preserve your configuration.
  </Warning>
</Accordion>

## Repository Not Appearing

If your repository doesn't show in the list:

<Accordion title="Check repository permissions">
  1. Go to GitHub → Settings → Applications → Jamdesk
  2. Verify the repository has access granted
  3. Click **Configure** to add more repositories
</Accordion>

<Accordion title="Organization 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
</Accordion>

<Accordion title="Private repositories">
  Private repos require GitHub authorization. Re-authorize Jamdesk if needed.
</Accordion>

## Builds Not Triggering

If pushes don't trigger builds:

<Steps>
  <Step title="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
  </Step>
  <Step title="Verify the branch">
    Builds only trigger on your configured branch. Check **Settings** in Jamdesk.
  </Step>
  <Step title="Re-sync the connection">
    1. Go to project **Settings** in Jamdesk
    2. Click **Re-sync GitHub**
  </Step>
</Steps>

## 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?

<Card title="Contact Support" icon="headset" href="/help/support/contact">
  Include your repository URL and error messages
</Card>

## Related Articles

<Columns cols={2}>
  <Card title="Error Reference" icon="book" href="/help/troubleshooting/error-reference">
    Full error code list
  </Card>
  <Card title="Contact Support" icon="headset" href="/help/support/contact">
    Escalate unresolved issues
  </Card>
</Columns>