Change the Git repository a service deploys from

A Voroa service builds from one repository, and you can change which one without recreating the service. The service keeps its name, URL, custom domains, environment variables, secret files and deploy history — only the source it builds from moves.

Change the repository

1. Open the service and go to Settings.
2. Under Build & Deploy, find Source and select Edit.
3. Pick a repository from your connected account.
4. Review what the confirmation tells you, then select Save.

Saving redeploys the service immediately from the new repository, and you can watch the build in the Deploys tab.

The branch is chosen for you

The branch you were deploying may not exist in the new repository, so Voroa does not carry it over blindly. If you pick a branch along with the repository, it is checked against the new repository first. If you do not, the new repository’s default branch is used.

You can change the branch afterwards at any time — see Branch and root directory.

What carries over, and what you may need to fix

Settings that describe the layout of a repository stay as they are, because they are your configuration and deleting them silently would be worse than leaving them. After the switch, check each one that applies to your service:

• Root directory — if your service builds from a subfolder such as /api, make sure that folder exists in the new repository. For a static site this is the folder that gets published.
• Build filters — path rules that decide which pushes trigger a build. A filter written for the old repository can match nothing in the new one, and then pushes stop deploying.
• Dockerfile path — if your service builds from a Dockerfile, the path must exist in the new repository.

Build and start commands, environment variables and secret files are unaffected.

Automatic deploys follow the new repository

If automatic deploys are on, pushes to the new repository deploy the service from the moment you save, and pushes to the old repository are ignored. If they are off, nothing deploys until you deploy the service yourself.

What you cannot change here

• A repository you have not connected. Only repositories shared with Voroa are listed. If one is missing, connect the account or grant access to that repository, then reopen the picker.
• Some older services cannot be moved to a different repository. If yours is one of them, Voroa says so when you save, and the way forward is to create a new service from the repository you want.

Live preview environments

Pull-request previews that are already running keep building the pull request they were opened for, and close as usual. New pull requests create previews from the new repository.