Volnyn – Website Builder, Domains, Property, Freelancers & Free Games
Open App

Sync your Volnyn site code with GitHub

Git sync pushes your AI site’s source into a GitHub repository you own, so you can back up code, collaborate with developers, work in your IDE, and deploy anywhere.

When you build with Volnyn, your project source lives in the AI builder workspace. Sync to GitHub connects an AI-built site to a repository on your GitHub account and lets you push the current source as a commit whenever you click Push to GitHub.

You don’t need Git to use Volnyn. Many people build and publish entirely inside Volnyn. Git sync is for backup, collaboration, and working outside the platform.

This page explains how the sync works. In a site, open GitHub in the site sidebar (/user/site/github).

Why sync your site to GitHub

  • Back up your code. Keep a copy outside Volnyn, in an account you control.
  • Collaborate with developers. Use branches, pull requests, and code review on GitHub.
  • Work locally in your IDE. Clone the repo, run npm install && npm run dev, edit, and commit on GitHub as usual.
  • Deploy outside Volnyn. Self-host or ship the same source to another host.

How Git sync works

Volnyn’s Git sync has two layers:

  1. A GitHub account connection — OAuth with the repo scope, stored as your GitHub connector. Connect once; any AI site can reuse it.
  2. A site ↔ repository link — each AI site links to one repository (owner/name) and one branch (usually main).

Once linked, each Push to GitHub collects the site’s current workspace source and writes a single commit on the linked branch.

Volnyn sync is one-way for now: Volnyn → GitHub. Commits you make only on GitHub do not automatically flow back into the Volnyn editor. Re-push from Volnyn when you want the repo to match the latest AI-built source.

What gets pushed

Each push sends source that you can clone and run yourself:

  • App source under src/ (and similar project files)
  • package.json and other config files the builder workspace exposes

It does not push:

  • node_modules, dist, build, .next, caches, coverage, etc.
  • .env and other secrets
  • Built production assets (the goal is source you can build yourself)

There is a safety cap on file count and size so runaway workspaces don’t hammer the GitHub API.

Set up sync

1. Connect GitHub

  1. Open an AI-built site.
  2. Go to GitHub in the site sidebar (/user/site/github).
  3. If GitHub isn’t connected yet, click Connect GitHub and finish OAuth.

Volnyn asks for the repo permission so it can create repositories and push code. You can disconnect the connector later from your account connectors.

You can also connect GitHub from the Connectors flow in chat; the same grant powers this page.

After GitHub is connected, choose one:

Option What it does
New repository Creates a repo under your account (private by default), then links it to this site
Existing repository Links a repo you already have

For an existing repository, pushing replaces the branch contents with this site’s files. Prefer an empty repo if you’re unsure.

After linking, the page shows the repo name, branch, and whether you’ve pushed yet.

3. Push to GitHub

Click Push to GitHub. Volnyn:

  1. Reads the current builder workspace files
  2. Creates one commit on the linked branch
  3. Saves last-push time and a link to the commit

Open View last commit to jump to GitHub.

Clone and run locally:

git clone https://github.com/OWNER/REPO.git
cd REPO
npm install
npm run dev

Unlinking

Unlink repository only clears the link on the Volnyn site:

  • Your repository stays on GitHub with all history and files
  • The site stays in Volnyn; future edits are not pushed until you link and push again

Unlinking never deletes code on either side.

You can link the same or another repository again later, then push the current source.

Limitations

  • AI sites only. Theme / non–AI sites don’t have builder workspace source to push.
  • GitHub only. There is no GitLab sync on this page.
  • One repository per site. Each site links to one owner/name at a time.
  • One branch. Push targets the linked branch (default from the repo, usually main).
  • One-way. GitHub → Volnyn pull is not automatic.
  • Manual push. Edits in Volnyn are not committed on every chat turn — click Push to GitHub when you want a backup.
  • Existing repos get overwritten on push. Don’t link a repo with unrelated history unless you intend to replace that branch’s tree.
  • Build the site first. If the workspace has no files yet, sync asks you to build once, then try again.

FAQ

Do I need to know Git to use this?
No. Connect GitHub, link a repo, and click Push to GitHub. Use Git knowledge later for branches, PRs, or CI/CD on GitHub.

Is this the only way to get my code?
Git sync is the dashboard path for an ongoing GitHub backup. You don’t need it just to publish the live site from Volnyn.

Does pushing publish my live site?
No. A push only updates GitHub. Your live site changes when you publish from Volnyn.

Does the repo include my database data?
No. The repository holds application source, not production database contents.

Can I import an existing GitHub app into Volnyn as a new AI site?
This flow is for exporting an AI site’s source to GitHub. Linking an existing repo means Volnyn will push its source into that repo — it does not turn an arbitrary GitHub project into a Volnyn AI site.

What happens if I disconnect GitHub OAuth?
Pushes will fail until you connect again. Linked repo metadata on the site may still show until you unlink; reconnect OAuth, then push.