Code hosting
GitHub
Each site's code lives in its own repository in your GitHub account.
LiveChecked against a real account and switched on.
What airepeat uses it for
- Lists what you already have there
- Creates new resources for you
Where it stands
Checked against the real GitHub organisation since October 2026: repositories created from templates, and AI tasks clone and push. Archiving is tested against recorded API behaviour only.
The key to create
A fine-grained personal access token for the account or organisation that will own your sites' repositories, with access to all repositories (new ones are created as you go).
| Permission | Why |
|---|---|
| Administration: read and write | Create, archive and unarchive repositories |
| Contents: read and write | Write site code and template files |
| Metadata: read | Required by GitHub for every token |
| Webhooks: read and write | Hear about pushes so deploys stay in sync |
All key permissions in the docs
Give each key the smallest access that works. Keys are encrypted at rest, only decrypted for the job that needs them, and never shown again after you save them.
Run your next site on your own servers
Free while in beta. Bring your own keys; you pay your providers directly.