Connections
- Who can use it
- Org admin (managers see status read-only)
- Where
- Admin → Integrations and Admin → Sync runs
DevGlimpse reads your GitHub data through the DevGlimpse GitHub App. You manage the connection on the Integrations page. Org admins connect organizations and choose which repositories sync. Managers can see the status but not change it.
For GitLab, Bitbucket, ticket trackers and incident tools, see Integrations.
Connect another GitHub org
You must be an owner of the GitHub organization.
- Go to Admin → Integrations.
- Click Add GitHub integration.
- Choose which repositories to track (see below).
- Click Install GitHub App. GitHub opens its install page.
- Pick the organization and confirm.
GitHub sends you back to DevGlimpse, signed in, with the organization attached to your workspace. The last 90 days of history start importing, and the dialog shows progress. Dashboards fill in as repositories finish.
The App asks for read-only permissions. No file contents or diffs are ever read. See GitHub App permissions.
If you are not an owner
In the same dialog, under Not an owner of the GitHub organization?, click Copy invite link and send the link to an owner. It takes them to GitHub’s install page for the App. They still have to be an owner of the organization for the install to complete.
If the App is already installed
If someone installed the App directly from GitHub, use Already installed the App on GitHub? in the same dialog and click Sign in again to complete it. This attaches the installation to your workspace.
Choose which repositories sync
Each connected organization has a Repositories synced setting:
- All repositories syncs every repository the installation covers, including forks and any added later.
- All repositories except forks skips forks everywhere: backfill, live updates, the nightly check and the dashboards. Forks you add later are skipped too.
- Only the repositories selected on GitHub syncs exactly what you pick on GitHub’s install page. Forks among them are not filtered.
To change it, open Admin → Integrations, find the organization and pick another option. DevGlimpse converges on the new choice and starts a backfill for repositories that are newly included.
Add or remove repositories
With Only the repositories selected on GitHub, change the selection in GitHub: change the repository access setting of the DevGlimpse App in your GitHub organization settings. If you remove a repository, DevGlimpse shows a notice that it no longer syncs. Grant access again if that was not intended, or dismiss the notice if it was.
Check backfill and sync status
Each organization card on Admin → Integrations shows its status (Active, Suspended or Disconnected) and a one-line backfill summary, such as how many repositories are done, running, queued, deferred by a rate limit, or failed.
For the full picture, click View sync runs or go to Admin → Sync runs. It lists every backfill, Teams import and Nightly reconcile with its status, start and finish time, and what each run stored. You can filter by workflow and status. A run can be Deferred while it waits for GitHub’s rate limit, or Paused — license while the license does not allow syncing.
After the backfill, live updates keep your data current. A nightly check at 02:00 UTC repairs anything a live update missed.
Reconnect
If the App is uninstalled or suspended on GitHub, the card shows a notice.
- Suspended. No new activity syncs until an owner of the GitHub organization unsuspends the App.
- Uninstalled. Sync stops. Install the App again and everything already stored is kept. The integration becomes Active again.
If every connected organization is uninstalled, the workspace goes read-only. See Data and deletion.
Other notices on the page tell you about new App permissions waiting for approval, sync failing for more than six hours, and sync waiting on GitHub’s rate limit. Each links to its fix.