Version control + collaboration + CI — where your exported InBuild code lives long-term.
After you export an InBuild project, push it to a GitHub repo and you've got version history, code review, GitHub Actions for CI, and the standard developer workflow. Treat the exported code like any other Next.js project — branches, PRs, deploys from main.
What you get
FAQ
How do I push an exported InBuild project to GitHub?
Unzip the export, `cd` into the folder, `git init`, `git add . && git commit -m 'initial export'`, then `gh repo create your-name/your-repo --private --push --source .` (or use the GitHub web UI to create the repo and add it as a remote).
Can I re-export later and keep my git history?
Yes. The InBuild export is deterministic for a given project state — files in the same locations. After re-exporting, copy the new files over your repo and commit. Diffs will show the AI-driven changes; you can review them like any PR.
Does InBuild push to GitHub automatically?
Not today — export is a manual zip download. Auto-push to a connected repo is on the roadmap.