Connecting a repo to the Turtini IDE

Before the IDE can edit anything, it needs a repo. Connecting one is a one-time setup per repo — picking it once, then it's available in the IDE's repo picker for future sessions.

Prerequisites:
• GitHub connected to your Turtini org (Settings → Integrations → GitHub) with read+write to the repos you want to use
• At least one repo with a build that produces a static-site output (any framework — Next.js export, Vite, Astro, plain HTML, …)

Picking a repo:
1. Open the IDE (/ide)
2. The repo picker shows every repo your connected GitHub user can access
3. Click a repo to start a session — files clone, the sandbox boots, the preview URL is provisioned
4. The session is bound to that repo until you click "Switch repo" or close it

Switching between repos:
Click "Switch repo" in the IDE header — your current session is saved (autosaved buffers + chat history persist) and you're returned to the picker. Picking a different repo starts a fresh session there. Switching back later restores everything.

Branching:
By default the IDE works on the repo's default branch. To work on a feature branch, switch the branch in the file tree's branch picker — the Monaco editor and preview both reload from that branch. Commits push to the active branch.

What's NOT supported:
• Submodules — the runner ignores them
• Repos larger than ~500 MB total — clone times become miserable
• Repos that need build secrets at compile time — set those as Turtini secrets (Settings → Secrets) and reference them via process.env in your build