Docs

Projects & Versions

Manage dashboard projects, versions, rebuilds, remix, GitHub sync, download/upload, and lifecycle operations.

Chapter 01

Versions

Every build is a version, and versions are the safety net that makes prompting a low-risk activity. v0 is the first generation; each prompt that changes files creates the next one.

Auto-fix
Stays on the current version. It is repairing the build you already have, so it does not create a new one.
Fix all
Creates a new repair version carrying the error context, so you can compare it against the broken one and roll back if the repair made things worse.
Rollback
Select an earlier version to return to it. Later versions are not deleted — you can go forward again.
Publish pins a version

Production serves the version you published, not the latest one. After rolling back in the editor, publish again if you want production to follow.

Chapter 02

Download and upload

  • Tools → Download exports the selected version as a ZIP. Code download depends on your plan.
  • Tools → Upload ZIP imports a React project ZIP, strips node_modules/dist, creates a version, and rebuilds preview.

Chapter 03

GitHub sync

Link a repository and branch, then use Pull to bring GitHub files into NeoBuild or Push to commit and upload your current version.

The usual working pattern is one person prompting in NeoBuild and a developer working in the repository. Pull before you push whenever the developer has committed since your last sync. Review the pull preview: matching files are replaced with GitHub content.

Review before pulling

Pull shows the affected files before applying changes. Files only in NeoBuild are kept by default. Publishing is a separate checkbox in the pull preview.

Full detail, including monorepo folder paths and the merge-versus-replace choice, is in Integrations & Ownership.

We use privacy-friendly analytics to understand how people find NeoBuild. No cookies are set unless you accept. Cookie Policy