GitHub
Connect GitHub and every website in 1DB shows the repository behind it and when its code last changed, so you can tell which of hundreds of sites are maintained and which have gone quiet.
- Read-only token
- Repos matched to sites
How it works
- 1
Make a read-only token
1DB opens GitHub’s token form for you. Set the resource owner to the account or organization that owns your repos and give it access to all repositories. No extra permissions are needed.
- 2
Paste it into Connections
The token is encrypted before it’s stored. Only its last characters are shown again, so you can tell tokens apart.
- 3
Repos are matched to sites
1DB looks through the repositories the token can see and links each one to the website it deploys, with the date of its latest change.
Good to know
- 1DB never pushes code with it
- The connection token is read-only. It lists repositories and nothing else.
- New sites
- When you add a site that isn’t live yet and choose to deploy it, 1DB creates its GitHub repo with the build prompt as the README and ships the first version to Vercel.
- Organization tokens
- A token for a GitHub organization may need an organization admin to approve it before it can see the repos.
Works alongside
- IntegrationBuild and watch sites
Vercel
See which Vercel project deploys each website and how its latest deploy went. New sites get a project with their keys already set.
- IntegrationBuild and watch sites
Cloudflare
See which Pages project or Worker serves each website, and which domains have their DNS on Cloudflare.
- IntegrationBuild and watch sites
PostHog
Pageviews and visitors for each website, next to its leads, refreshed hourly. Traffic that stops or spikes is flagged.