Title: Deploying branches
Author: WordPress VIP Documentation
Published: September 28, 2023
Last modified: June 25, 2024

---

 1. [Code deployment](https://docs.wpvip.com/code-deployment/)
 2. [Default Deployment](https://docs.wpvip.com/code-deployment/default-deployment/)
 3. Deploying branches

#  Deploying branches

Each of an application’s VIP Platform environments can track its own specific branch
of [the application’s wpcomvip GitHub repository](https://docs.wpvip.com/wpcomvip-github-repository/).

When [Default Deployment](https://docs.wpvip.com/code-deployment/default-deployment/)
is enabled for a WordPress or Node.js environment:

 * [The branch deploying to the environment can be updated](https://docs.wpvip.com/github-repository/deploying-branches/update/)
   in the **Repository Management** panel of the VIP Dashboard.
 * [Continuous integration and deployment (CI/CD)](https://docs.wpvip.com/development-workflow/automated-build-and-deploy/)
   methods can be set up for a deploying branch.
 * Incorporating a [GitHub pull request flow with a review stage](https://docs.wpvip.com/development-workflow/github-pr-reviews/)
   is strongly recommended for the branch that deploys to a production environment.

## Branch protection rules

By default, all wpcomvip GitHub repositories are set up with basic [branch protection rules](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches).
These include a rule to prevent a branch from being deleted, and a rule to prevent
force-pushes for all non-Admin users. Only GitHub users with Admin permissions have
the ability to modify the branch protections rules. For more information, review
[GitHub’s documentation on Managing a branch protection rule](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule).

Last updated: June 25, 2024