All integrations
Source control
GitHubOne-click
See what each deploy contains, what a rollback would undo, open pull requests and whether CI passes.
What you see
Source control
On the Deployments page as soon as GitHub is connected.
How to connect
Sign in at GitHub
Connections sends you to GitHub’s own consent screen, then asks what to connect. Baseboard asks for no extra scopes. What the sign-in hands back is sealed like a key before it’s stored.Or paste a key
A fine-grained token (github_pat_…) for this one repository, with read access to Contents, Pull requests, Commit statuses and Actions. For an organization's repository, choose the organization as resource owner; an owner may have to approve it. CI shows from Actions and commit statuses; other apps' check runs need one-click connect. Get a key The key is checked against GitHub before it’s saved, then sealed so only the broker that calls GitHub can open it.From a terminal
The CLI asks for the same key at a hidden prompt, so an agent running it never sees the key.$ npx baseboard-cli connect github --project k57abc
Settings
- Repositoryrequired
- owner/name, as in the repository URL.For example
acme/web
Connect GitHub and the rest of your stack in one place.
Free covers one project with three connections. Everyone starts read-only.