Span reads GitHub through a read-only GitHub App. How you connect depends on where your GitHub lives. Use the table to pick the right one, then follow the matching setup guide.

Which one do I use?

Not sure which you have? Look at the URL you use to view your repositories. github.com/your-org → GitHub. A ghe.com subdomain → GitHub Enterprise → Cloud (with data residency). A private hostname → GitHub Enterprise → Server.

GitHub (Cloud on github.com)

The standard integration for any organization on github.com, including a GitHub Enterprise Cloud plan on github.com. There is no separate tile for the Enterprise plan — the URL is what matters.

1. Settings → Tools & Integrations → Connect next to GitHub.

2. Authorize Span’s GitHub App and choose all or selected repositories.

3. Connect again to add another organization; one workspace can hold several.

See Integrating GitHub with Span.

GitHub Enterprise (Server or Cloud with data residency)

Both live under the GitHub Enterprise tile. Under GitHub App Creation, choose the Deployment:

• Server — self-hosted on your own infrastructure, e.g. github.company.com.

• Cloud (with data residency) — hosted by GitHub on your ghe.com subdomain, e.g. your-org.ghe.com.

Then enter the hostname (hostname only, no https://) and the app-owner organization, and click Create GitHub App. GitHub redirects back to Span; when the status shows Created, use Connect to install the app on each organization. The app is public on your instance, so it can be installed across multiple organizations there.

GitHub Issues

GitHub Issues is a project-management source, not a separate VCS connection. It rides on the same GitHub App installation as the GitHub integration, so connect GitHub first. Use it when GitHub Issues is where your team tracks work and you want issue cycle time, issue volume, and PR-to-issue links.

What about Copilot?

GitHub Copilot is not a separate connection. It is a toggle on an existing GitHub connection that adds Copilot seat and usage data. See the GitHub Copilot Integration Guide.

Notes

• Every option uses a read-only GitHub App. Span never writes to GitHub.

• For Server, your network team may need to allow Span’s outbound IPs — see Network Access Requirements.

• You can mix options: e.g. connect GitHub for cloud orgs and GitHub Enterprise → Server for a self-hosted instance in the same workspace.