Deploying branches

Each of an application’s VIP Platform environments can track its own specific branch of the application’s wpcomvip GitHub repository. If the branch deploying to an environment needs to be changed, create a VIP Support request for assistance.

• Incorporating a GitHub pull request flow with a review stage is strongly recommended for the branch that deploys to a production environment.
• Continuous integration and deployment (CI/CD) methods can be set up for a deploying branch.
• It is possible to update the name of the branch deploying to production (which as of 13 January 2023 is production by default). To do so, specific steps must be followed in coordination with the the VIP Support team team to ensure that the process is successful.

Branch protection rules

By default, all repositories are set up with basic GitHub branch protection rules. 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.