Home GitHub Connector

GitHub Connector

Find help on connecting your GitHub account, syncing repositories, and managing projects within Everdone.
By Urvisha
• 11 articles

How do I add a GitHub connector?

Short Answer: Go to Settings > Connectors, click Add connector, choose GitHub App (Recommended) or GitHub OAuth, click Connect, complete the GitHub authorization, then confirm the connector shows Connected in the table. Answer Prerequisites 1. Be signed in to Everdone 2. Open Settings > Connectors 3. Have a GitHub account (with access to the repos you want to connect) 4. For GitHub App installs: you need organization owner or admin access on GitHub Steps 1. In Everdone, open Settings > Connectors. 2. Click Add connector. 3. Under Connect using: select GitHub App (Recommended) or GitHub OAuth. 4. Click Connect to start the GitHub flow. 5. In GitHub, approve the requested permissions (and select the org/repos if prompted). 6. Return to Everdone and verify the connector appears in the Connectors table with Status: Connected (columns typically include Account, Type, Status, Last synced). Troubleshooting 1. I can’t install the GitHub App. - Likely Cause: App installs require GitHub organization owner/admin permissions. - Action: Ask an owner/admin to install the App, or use GitHub OAuth instead. 2. Connect doesn’t finish or shows an error. - Likely Cause: GitHub authorization was denied or not completed. - Action: Re-run Connect and complete all GitHub prompts (authorize/install, select org/repos). 3. I don’t see the Add connector button. - Likely Cause: You’re not on the Connectors page. - Action: Open Settings > Connectors and try again. Notes - The GitHub App path offers finer-grained, organization-level control and is recommended. - The connect modal explicitly states the admin requirement for App installs.

Last updated on Oct 14, 2025

What happens when I disconnect a GitHub account?

Short Answer: Access is limited to the repositories you selected during setup and by the permissions (OAuth scopes or GitHub App install settings). Check the “Only selected repos are accessible.” note and review the connector’s scopes/permissions in the account details. Answer Prerequisites 1. A GitHub connector is listed under Settings > Connectors 2. You can open the GitHub account details dialog Steps 1. Go to Settings > Connectors and open the account details for your GitHub connector. 2. At the top, look for “Only selected repos are accessible.” Then review the Repositories accessed table to see exactly which repos/branches are available. 3. Review the OAuth scopes (or App permissions) shown in the dialog to confirm the connector has repo access (e.g., repo / read). 4. If you recently changed permissions, run a manual sync (Actions → Sync now) to refresh the list. 5. If needed, re-authorize with broader scopes or ask a GitHub org owner/admin to update the GitHub App installation to include additional repositories. Troubleshooting 1. A repo I need isn’t listed. - Likely Cause: It wasn’t selected during App install/OAuth, or the connector lacks permission. - Action: Update the GitHub App installation to include that repo (owner/admin required) or reconnect with the required OAuth scopes, then Sync now. 2. OAuth scopes don’t include repo access. - Likely Cause: The account was authorized with limited scopes. - Action: Reauthorize the connector ensuring repo access (e.g., repo / read). Consider using the GitHub App with proper permissions if you manage multiple org repos. Note: The account details dialog shows the exact text “Only selected repos are accessible.” and lists the current OAuth scopes or App permissions for that connector.

Last updated on Oct 14, 2025

What connection types are available for GitHub and when should I use each?

Short Answer: Use GitHub App (Recommended) for organization-level installs (requires a GitHub owner/admin to install, lets you choose org/repos with fine-grained, revocable permissions). Use GitHub OAuth for personal repos or org repos you already access without needing admin approval. Prerequisites 1. Open the Add connector modal (Settings > Connectors > Add connector) Steps 1. Go to Settings > Connectors and click Add connector. 2. Under Connect using: review the two options: - GitHub App (Recommended): Org-level installation, granular permissions, select specific repos/orgs; installable only by GitHub owners/admins. - GitHub OAuth: User-authorized access to repos you personally can access; no org-wide install needed. 3. Select the option that fits your needs and click Connect to start the flow. When to choose which - Choose GitHub App if: - You need to connect multiple org repositories with centralized control. - You want fine-grained permissions and easy revocation per org/repo. - You can get a GitHub owner/admin to approve the install. - Choose GitHub OAuth if: - You’re connecting personal repos or a few org repos you already have access to. - You don’t have admin rights for an org-level install. - You need a quick, user-scoped connection. Troubleshooting 1. Need org repos but can’t install the App - LikelyCause: App installs require GitHub owner/admin permissions. - Action: Ask an org owner/admin to install the App, or use OAuth for repos you already have access to. Note: Exact UI labels in the modal: “Connect using:”, “GitHub App (Recommended)”, “GitHub OAuth.”

Last updated on Oct 16, 2025

Where can I see a connector’s details, OAuth scopes, and repo access?

Short Answer: Go to Settings > Connectors, then click the details/document icon in the connector’s Actions column to open GitHub account details. The modal shows Account info, Connection details, OAuth scopes/App permissions, and Repositories accessed. Prerequisites 1. Be signed in with view access to Settings > Connectors 2. A connected GitHub account appears in the Connectors table Steps 1. Open Settings > Connectors and find the GitHub connector row (columns include App name, Account, Type, Status, Last synced, Actions). 2. Click the details/document icon in Actions. The GitHub account details modal opens. 3. Review the sections: - Account info - Connection details (Status, Connection type, Connected on, Last synced) - OAuth scopes / App permissions - Repositories accessed (repos/branches listed) 4. Click Close to return to the Connectors table. Troubleshooting 1. A repo I expect isn’t listed - LikelyCause: Only selected repos are accessible, or scopes/permissions are too limited. - Action: Check Repositories accessed and OAuth scopes/App permissions in the modal; update permissions in GitHub or Sync the connector, then re-check. 2. Status shows not connected or “Last synced” is stale - LikelyCause: Authorization was revoked/expired, or a sync is needed. - Action: Click the sync (circular arrows) action or reconnect the account. Note: The modal header reads “GitHub account details” and indicates “Only selected repos are accessible.

Last updated on Oct 16, 2025

Why are some repositories not accessible or missing after I connect GitHub?

Short Answer: Access is limited to the repos you selected during setup and by the connector’s permissions (OAuth scopes or GitHub App install settings). Open account details, note “Only selected repos are accessible.”, and review scopes/permissions and the Repositories accessed list. Prerequisites 1. A GitHub connector appears under Settings > Connectors 2. You can open the GitHub account details dialog Steps 1. Go to Settings > Connectors and open GitHub account details for your connector. 2. At the top, confirm the note “Only selected repos are accessible.” 3. Review Repositories accessed to see exactly which repos/branches are available. 4. Check OAuth scopes / App permissions to confirm repo access (e.g., repo / read). 5. If permissions were just changed, run a manual sync (Actions → Sync now) to refresh. 6. If needed, reauthorize with broader scopes or ask a GitHub org owner/admin to update the GitHub App installation to include additional repositories. Troubleshooting 1. A required repo isn’t listed - LikelyCause: It wasn’t selected during App install/OAuth, or the connector lacks permission. - Action: Update the GitHub App installation to include that repo (owner/admin required) or reconnect with the required OAuth scopes, then Sync now. 2. OAuth scopes don’t include repo access - LikelyCause: The connector was authorized with limited scopes. - Action: Reauthorize the connector ensuring repo access (e.g., repo / read). If managing many org repos, consider using the GitHub App with proper permissions. Note: The account details dialog shows the exact text “Only selected repos are accessible.” and lists the current OAuth scopes/App permissions for that connector.

Last updated on Oct 16, 2025