Getting started / Connect your repository

Connect your repository

A repository connection lets the assistant make code changes — styling, components, schema — by committing to a branch you choose. It's optional: content-only workspaces work fine without one.

GitHub

Create a fine-grained personal access token: GitHub → Settings → Developer settings → Fine-grained tokens → Generate new token. Under Repository access select only your site's repository; under Permissions grant Contents: Read and write.

If the repository belongs to an organisation, an org admin may need to approve the token before it works — until then the repo can look like it doesn't exist (a "not found" error). If your connection test fails with a valid token, ask an org admin to approve it under the organisation's token settings.

GitLab

In your project: Settings → Access tokens → create a Project Access Token with the api and write_repository scopes, role Developer or above (tokens start glpat-). Enter the project path as group/project.

Bitbucket

Personal settings → App passwords → create one with Repositories: Read and Write. You'll enter your Bitbucket username plus that app password.

Branches

You set a production branch (usually main) and, optionally, a staging branch. With a staging branch connected, the typical flow is code-to-staging first: the assistant suggests staging for code changes by default, and your roles can even restrict certain users to staging only — see Environments.

Commits trigger your host's automatic rebuild, so code changes are typically live on the target branch's site in 30–60 seconds.

← Connect your CMS Hosting & deploys →