Skip to content
Zeyo Host

Signed in

Dashboard Billing Help

Hosting

Get started Log in
Go to dashboard

Git™ Version Control

Clone a Git repository from GitHub, GitLab or another host, pull new changes, switch branches and deploy the files to a website.

Reference Checked against panel v2.3.2 Updated 11 Oct 2026 · 5 min read Open in your panel

Git™ Version Control keeps a copy of your site's code repository on your hosting account. Clone it once, then pull new changes whenever you push them, switch to another branch, and deploy the files into a website's public_html. Each repository lives in its own folder of your home folder, by default under repositories, and reaches a website only when you deploy it.

Clone a repository

  1. In the panel, open Files → Git™ Version Control.
  2. Repository address: paste the repository's address. Public repositories work with their https:// address, such as https://github.com/you/site.git. For a private repository, use its SSH address, such as [email protected]:you/site.git, and a deploy key (see below).
  3. Folder (from your home folder): where the repository goes. The panel suggests repositories/ followed by the repository's name. The folder must not exist yet.
  4. Branch (optional): the branch to check out, such as main. Leave it empty for the repository's default branch.
  5. Click Clone.

Cloning runs in the background. A strip at the top of the page shows it is in progress, and the repository appears under Your repositories when it finishes.

The Git Version Control page with the Clone a Repository form and the Your repositories table showing each repository's folder, branch and last change.The Git Version Control page with the Clone a Repository form and the Your repositories table showing each repository's folder, branch and last change.

Use a deploy key for a private repository

A deploy key is a key made for one repository folder. Once you add it to the repository, the server can read the repository with it.

  1. Enter the SSH address and the folder in the clone form.
  2. Click make one for this folder. The page shows the Deploy key for that folder.
  3. Copy the key and add it to the repository as a deploy key: on GitHub under Settings → Deploy keys, on GitLab under Settings → Repository → Deploy keys. Read-only access is enough.
  4. Back in the panel, click Clone.

To see the key again later, click Deploy key next to the repository in the list.

Pull new changes

  1. Find the repository under Your repositories.
  2. Click Pull.

The pull runs in the background. When it finishes, Last change shows the newest commit. Pulling updates the repository folder only; deploy it to update your website.

Switch branch or deploy to a website

  1. Click Manage next to the repository.
  2. To change branch, choose it under Switch to branch and click Switch.
  3. To publish the files, choose the website under Deploy the files to, click Deploy and confirm with Deploy.

Deploying copies the files of the checked-out branch into that website's public_html. It runs in the background.

Stop listing a repository

  1. Click Forget next to the repository.
  2. Confirm with Forget.

The repository is removed from the list, but its folder and files are kept. Delete the folder in the File Manager if you no longer need it.

Common errors

Message Why What to do
Use an https:// address, or an SSH one like [email protected]:you/site.git. The address is not an https:// or SSH address. Copy the address from the repository host's Clone button.
Folder names can use letters, digits, dots, dashes and underscores, and cannot start with a dot or dash. The folder has spaces or other characters, or a name in it starts with a dot or dash. Choose a folder name without them, such as repositories/site.
That is not a branch name. The branch has characters Git does not allow, or no branch was chosen. Check the branch name, or choose one from the list.
That item already exists. The folder already exists. Choose another folder.
Git could not clone that address. Check it, and for a private repository that its deploy key (shown here) was added to it with read access. The address is wrong, or the private repository does not have this folder's deploy key. Check the address, add the deploy key to the repository, then clone again.
Git could not pull: the copy here has local changes, the branches have diverged, or the remote refused the deploy key. Files in the repository folder were changed on the server, the history cannot be updated directly, or the deploy key was removed from the repository. Undo the changes on the server, or clone the repository again into a new folder. Check the deploy key is still on the repository.
Git could not switch to …: the copy here has local changes, or there is no such branch. Files in the repository folder were changed on the server, or the branch does not exist. Undo the changes on the server, pull, then try again.
The files could not be written to …'s public_html (check the folder's permissions, or use Fix Home Permissions). The server could not write into the website's public_html. Run Fix Home Permissions, then deploy again.
That website is not yours. The website is no longer on your hosting account. Reload the page and choose a listed website.
That item does not exist. A folder above the one you entered does not exist, such as projects in projects/site. Use a folder under repositories, or create the folder above first.
That repository is not on your account. The repository was forgotten in the meantime. Reload the page.
… is already in progress. Please wait for it to finish. The same clone, pull or deploy is already running. Wait for it to finish.
This tool needs the Zeyo agent 1.2.0 or later on your hosting server, which it does not have yet. Please contact support to have it updated. Your hosting server needs an update before the tool can run. Contact support and quote the message.

Related

Was this page helpful?

Sent without cookies; we do not store your IP address.

Still stuck? Contact the team; tell us the page and what you see.