Git, import and export

Ninoo Git

Every project has a private git repository on Ninoo Git, our own git server. It always has your project's full history. Everyone on the project gets access that matches their role: editors can push, viewers can only read.

1. 01

   Sign in to Ninoo Git

   Open git.ninoo.ai and choose Sign in with Ninoo. It uses your Ninoo account; there's no separate sign-up.
2. 02

   Make an access token

   In Ninoo Git, go to Settings → Applications and create a token with repository access. Git asks for it as your password.
3. 03

   Clone

   Copy the command from More → Ninoo Git in the Builder and run it on your computer.

git clone https://git.ninoo.ai/<owner>/<project>.git
cd <project>
# change something, then:
git add -A
git commit -m "Tweak the footer"
git push origin main

What happens when you push

• Push to main: Ninoo merges it into the app, combining it with any changes made in the Builder meanwhile. It shows in History as “Merged branch”.
• Push another branch: it waits under More → Ninoo Git → Pushed branches. Editors can press Merge into the app or Dismiss it.
• main is protected: force-pushes and deleting it aren't allowed, so history can't be lost.

Import a project

Open app.ninoo.ai/import to bring in a project you started somewhere else. It becomes a normal Builder project that you keep building by chat.

• From GitHub: paste the repository address, like https://github.com/you/your-app, and optionally a branch. For a private repository you also paste a GitHub token once; it's used for the download and never stored.
• From a ZIP file: up to 40 MB. Leave out node_modules, build output and large media to stay under the limit.
• From Lovable: download your project from Lovable, or connect it to GitHub, then import it either way. See Switch from Lovable.

Vite + React projects work best. Other setups import too, on a best-effort basis. On the first prompt after an import, Ninoo gets the app running in the workspace and explains what it does, without restyling or restructuring it unless you ask.

Download and export

The owner can take the code out under More → Download & GitHub.

• Download .zip: the whole project, including .env unless your project's .gitignore excludes it (imported projects usually do). Keep the file private.
• Push to GitHub: a one-off push to a repository of yours, using a GitHub token you paste. .env is never sent. New repositories are private unless you tick “Make a new repository public (existing repositories keep their visibility)”.
• node_modules, build output and Ninoo's own history files are always left out. Your full history is on Ninoo Git.