GitHub sync

Your code belongs to you. GitHub sync puts it in a repository under your GitHub account, where you can clone it, review history, open pull requests or take it anywhere else.

Connecting

The first time you sync, Qyant asks you to authorise it with GitHub for repository access. You can revoke that at any time from GitHub's application settings; syncing will simply stop working until you authorise again.

If you signed up with GitHub, the connection is already there.

Syncing

Project menu → Sync to GitHub. On first sync Qyant creates a repository (private by default) named after the project and pushes the current version to main. Later syncs push a new commit with the changes since the last one.

The project header shows the linked repository. The repository name and default branch are visible on the project card.

What is pushed

Every project file except .env. Secrets never leave Qyant this way. A .gitignore is part of the template so node_modules and build output stay out too.

What is not synced back

Sync is one-way: Qyant → GitHub. Commits you make in the repository are not pulled into the project. If you want to keep working in Qyant after editing elsewhere, bring the change back through a prompt or the editor.

Running the project elsewhere

The repository is a standard Next.js app:

git clone git@github.com:you/your-app.git
cd your-app
cp .env.example .env   # set DATABASE_URL to a Postgres you own
npm install
npm run dev

Nothing in the generated code depends on Qyant.