Deploy from GitHub, GitLab, Bitbucket or any Git address

Connect a repository to your site and every push to its branch puts a new version online. You can connect GitHub, GitLab or Bitbucket, or any Git repository by its address. Only the workspace’s owners and admins can connect a repository.

Connect a repository

You can connect one when you create a site (on the console’s Home page, under Import from a repository, choose GitHub, GitLab, Bitbucket or Another Git host), or later from an existing site: open it, go to its Settings tab and find Repository.

GitHub

1. Click Connect GitHub, then Continue with GitHub to sign in. This only reads the list of your repositories.

2. If asked, click Install on GitHub and install Cloudzyro on the account or organisation that owns your repository. We suggest choosing only the repositories you want to deploy.

3. Choose the Repository and its branch.

4. If your site isn’t at the top of the repository, fill in Folder, for example apps/web.

5. Click Deploy site.

Cloudzyro can read your repository’s files and marks each commit on GitHub with whether it went live. It never changes your code.

GitLab

1. Click Connect GitLab, then Continue with GitLab to sign in.

2. Choose the project and its branch. Only projects where you’re a Maintainer or Owner are listed.

3. If your site isn’t at the top of the project, fill in Folder.

4. Click Deploy site.

We add a webhook and a read-only deploy key to the project, so pushes go online by themselves.

Bitbucket

1. Click Connect Bitbucket, then Continue with Bitbucket to sign in.

2. Choose the repository and its branch. Only repositories you’re an admin of are listed.

3. If your site isn’t at the top of the repository, fill in Folder.

4. Click Deploy site.

We add a webhook and a read-only access key to the repository, so pushes go online by themselves.

Git address

Use this for any other host, such as Codeberg or your own Git server.

1. Under Or connect by its Git address, paste the Repository address. Copy it from your browser’s address bar or the Clone button.

2. If it’s private, tick It’s a private repository and paste a Read-only access token. Add a User name only if your host gave you one with the token. We keep the token encrypted and use it only to fetch this repository.

3. Click Find branches, choose the Branch, and fill in Folder if your site isn’t at the top of the repository.

4. Click Deploy site. We deploy the branch’s newest commit.

5. To make every push go online by itself, open the site’s Settings, click Make a webhook address, copy it and add it as a webhook on your repository with push events. We show the address only once. Keep it private: anyone with it can start a deploy of your latest commit. If you lose it, make a new one and the old one stops working.

Until the webhook is on your repository, click Deploy latest commit to put a new version online.

How automatic deploys work

Each push to the connected branch becomes a new version, built and put online the same way as an upload. Your current version stays online until the new one is ready. You can follow each deploy on the site’s Versions tab.

While a site is connected to a repository, new versions come only from it: uploads and AI tools can’t deploy the site. To use them again, disconnect the repository first.

Change the branch or folder

In the site’s Settings, under the repository:

• GitHub: click Change branch or folder, choose the new branch or folder, then confirm. We deploy from the new branch straight away.
• GitLab, Bitbucket and Git addresses: click Change folder to change the folder. It applies from the next push or Deploy latest commit. To deploy from another branch, disconnect and connect the repository again.

Pause automatic deploys

To stop pushes going online for a while, open the site’s Settings and click Pause automatic deploys. Pushes are then ignored until you click Resume automatic deploys. Deploy latest commit still works while they’re paused.

To pause every site in a workspace at once, for example during a code freeze, go to Settings, Advanced and click Pause automatic deploys under Automatic deploys. Click Turn back on when you’re ready.

Disconnect a repository

In the site’s Settings, click Disconnect. Your site stays online with its current version, and its versions are kept.

• GitHub: nothing changes on GitHub. To remove Cloudzyro’s access to the repository, change it in your GitHub settings.
• GitLab and Bitbucket: choose Disconnect and remove to also remove our webhook and deploy key from the project (you may be asked to sign in first), or Just disconnect and remove them yourself in the project’s settings.

Tip

If Cloudzyro loses access to the repository (for example, it’s removed from the GitHub app, or a token expires), the site’s Settings tell you. Your site stays online as it is until you fix it.