Visual Editor /Cloud project /

Git branching

Visual Editor cloud projects interact with branches in your remote Git repository. Cloud projects work with two Git branches — a target and working branch.

# Target branch

The target branch is the one the visual editor uses to deploy the live site. This is also the branch where code is merged when publishing.

This defaults to the default branch of the repository (e.g. main or master) when creating a new project.

# Working branch

Visual Editor uses the working branch to run your site in the container. This is the branch that content editors work with.

This branch name defaults to preview, which gets automatically created when a new cloud project is created.

Learn more about changing the working branch.

# External updates

Visual Editor uses webhooks to listen for updates to the working branch in its remote repository, then immediately updates the local branch.

# Branch synchronization

The target branch is only used during the publishing process.

Keeping the working branch in sync with changes committed to the target branch must be handled separately. This process may be able to be automated, depending on your preferred workflow.

# Configure branches

You can override these defaults in the advanced settings when creating a new project from GitHub.

Target and Working Branch settings.

# Change working branch

You can also adjust the working branch after creating a project through the advanced settings.

  1. From Visual Editor dashboard, select your chosen project.
  2. From your chosen project, select the gear icon next to your project name. Next, select the Publish tab.

Can’t find visual editor settings?

We’re rolling out new visual editor settings. If you can’t find your visual editor settings, go to


Or select the new settings icon next to your project name and choose Visual editor settings.

  1. Choose an existing branch to use as the working branch. Note that you will not find the target branch as an option. You must work on a separate branch.


Be sure to verify you're working with the correct branches before starting to edit and publish content.