How to connect GitHub
Commit articles as files to a repo (Vercel, Lovable, any static blog).
The repo, the live site, and a token that writes to that one repo.
3 steps · 0:34 · silent, no sound to turn on
Open the repository on GitHub
The setup guide, in full
Word for word what the connect form asks, in the order it asks. Nothing here wants your GitHub password — the credentials below are ones you create and can revoke.
- 1
Which repository?
The repo your site builds from.
- 1Open the repository on GitHub.
- 2Copy the owner/name part of the address, e.g. acme/marketing-site.
- 2
Where does that repo publish to?
We check every published post is reachable there.
- 1Copy the address visitors use, e.g. https://www.acme.com.
- 2If the blog is under a path or a subdomain, enter that.
- 3
Create a GitHub token
It can write to this one repo and nothing else.
Open GitHub, filled in- 1Open GitHub with the button. The name and permission are filled in.
- 2Under Repository access, choose Only select repositories and pick this repo.
- 3Click Generate token, copy it, and paste it below.
- 4
Optional settings
Where files go and how branches are used. The defaults work for most setups.
If it doesn’t connect
The checklist the connect form shows when a test fails. Check each one in order.
- The repository is spelled exactly as owner/repo.
- The token is fine-grained, includes this repository, and has Contents: Read and write.
- The token has not expired.
- If an organization owns the repo, the organization is the token's resource owner and has approved the token.
Ready to do it for real?
Open your website in SearchBlueprint, go to Publishing, and pick the GitHub tile. The form walks these same steps, and tests the credentials against GitHub before it stores anything.
Connect GitHub