Skip to content

Update an environment’s deploying branch

Environments on WordPress VIP are set up to track a specific branch of an application’s GitHub repository. For example, new production environments are set up to track a branch named production by default. Pushing any changes to this branch (via a push, merge, or rebase) triggers an automatic deployment to the production environment.

The branch of an application’s wpcomvip Github repository that deploys to an environment can be updated in the VIP Dashboard.

Access

Prerequisite

To change an environment’s deploying branch, a user must have at minimum an Org admin role or an App admin role for that application.

  1. Navigate to the VIP Dashboard for an application.
  2. Select an environment from the environment dropdown located at the upper left of the VIP Dashboard.
  3. Select “Code” from the sidebar navigation at the left of the screen.
  4. Select Repository from the submenu.

Update the deploying branch

In the “Repository Management” VIP Dashboard panel:

  1. In the field labeled “Branch Name“, enter the name of the repository branch that should deploy to the environment after the update.
  2. Select the button labeled “Change Branch and Deploy“.

A successful update to the deploying branch will result in a code deployment to the environment.

If the branch name entered in the field does not exist in the application’s GitHub repository, the process will fail and no code deployment will occur.

The progress of the code deployment of the updated branch can be monitored in the Deployments panel for that environment.

Last updated: January 31, 2024

Relevant to

  • Node.js
  • WordPress