Skip to content

wpcomvip GitHub repository

Every WordPress and Node.js application hosted on WordPress VIP is supplied with its own GitHub repository within the wpcomvip GitHub organization. The URL for the application’s GitHub repository is typically the wpcomvip GitHub URL followed by a slug version of the application’s name. For example, the repository URL for an application named “My New Application” will likely be:

Once an application’s repository is created, it is ready to be used for development.

Only a repository within the wpcomvip organization can deploy to a VIP Platform environment. It is possible to use services such as Bitbucket, Beanstalk, or a separate GitHub repository to develop code and then push the code to the VIP application’s provided wpcomvip GitHub repository.


The wpcomvip GitHub repository is owned by the WordPress VIP organization. As a result, there are limitations on how it can be used.

  • As a security control, GitHub and OAuth Apps cannot be added to these repositories.
  • At this time, GitHub Actions are only available for use by FedRAMP customers.
  • By default, this repository is private but can be public if desired.
  • A repository slug can only be used once within the wpcomvip organization. As a result, it is possible that the desired slug for an application’s repository is not available to new customers and an alternate will need to be found.

User access

Customers are responsible for managing GitHub user access for their team members.

For increased security, access for VIP team members to an application’s GitHub repository is restricted and managed via GitHub teams. The following VIP GitHub teams will appear in a repository’s “Collaborators and teams” access list and must not be removed:

Deploying branches

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

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.

A wpcomvip GitHub repository associated with a customer organization can deploy to more than one of their applications. Create a VIP Support request if this configuration is desired.

Continuous integration and deployment (CI/CD) methods can be set up for a deploying branch.

Code deployments

Last updated: September 19, 2023

Relevant to

  • Node.js
  • WordPress