Source control

Clone your brand's repository, push changes from your own editor, and pull them into the live preview.

Every brand you create in Iterant is backed by a real Git repository. Terra commits to it as it works, and you can clone it, edit locally, and push back. The site Terra builds and the code you write are the same repository, so there is no import step and no export step.

Everything here lives at Settings → Source Control for the brand you are working on.

Early access

Connecting an account, cloning, pushing, and syncing all work as described. A repository is created per brand and cannot currently be relocated to your own GitHub organization.

Connect your GitHub account

Click Connect GitHub. You will be sent to GitHub to authorize Iterant, and returned to the Source Control page. Authorizing grants your GitHub account push access to this brand's repository straight away, so there is no invitation to accept by hand.

Each person connects their own account. Connecting yours does not give access to anyone else on your team, and the account you authorize with is the one that receives access, so make sure you are signed in to GitHub as the right user before you start.

Clone the repository

Once connected, the page shows an HTTPS and an SSH clone URL. Either works:

git clone https://github.com/<org>/<your-brand-repo>.git
cd <your-brand-repo>

The repository is a complete site: content entries, components, styles, and configuration. It builds and runs the same way locally as it does in your preview.

Push your changes

Work as you normally would, then push to main:

git commit -am "your change"
git pull --rebase --autostash origin main
git push origin main

Rebase rather than merge. Terra commits to the same branch while you work, so rebasing keeps main linear and keeps your history readable. --autostash lets you pull with uncommitted work in the tree.

Pull your push into the preview

Pushing to GitHub does not by itself update the site you see in Iterant. Your brand keeps a working copy that serves the live preview, and it needs to be told to catch up. Click Sync from GitHub and it will fetch your commits and reset the preview to match main.

Sync discards unsaved agent drafts

Sync resets the working copy to main, so anything Terra had drafted but not yet committed is lost. The confirmation tells you when that happens. If Terra is mid-task, let it finish before syncing.

If Terra is actively working when you press it, the sync is refused rather than queued. Wait for the turn to finish and try again.

Manage who has access

The Collaborators list shows everyone with push access to this brand's repository, with the GitHub account each one connected. Access is granted per brand, so a teammate with access to one brand does not automatically get access to another.

Collaborators receive push access only. They cannot delete the repository or change its settings. Use Revoke to remove someone; their access is withdrawn from GitHub immediately.

What Terra does while you work

Terra keeps committing to the same repository. It does not open pull requests or work on a branch, so treat main as shared. In practice this means pulling before you start, rebasing before you push, and syncing afterwards so the preview reflects what you pushed.

If you and Terra edit the same file at the same time, Git resolves it the way it resolves any conflict between two authors: your rebase will surface it, and you fix it locally before pushing.