Title: GitHub repository
Author: WordPress VIP Documentation
Published: February 27, 2023
Last modified: February 25, 2026

---

 1. [Code deployment](https://docs.wpvip.com/code-deployment/)
 2. GitHub repository

#  GitHub repository

Every WordPress and Node.js application hosted on WordPress VIP is supplied with
its own GitHub repository within the [wpcomvip GitHub organization](https://github.com/wpcomvip).
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:
`https://github.
com/wpcomvip/my-new-application`

 * **For WordPress applications**, [the GitHub repository](https://docs.wpvip.com/vip-codebase/)
   is initialized as a fork of the [vip-go-skeleton](https://github.com/Automattic/vip-go-skeleton)
   repository. Any code pushed to the WordPress application’s repository in a GitHub
   pull request is analyzed by the [VIP Code Analysis Bot (the Bot)](https://docs.wpvip.com/vip-code-analysis-bot/)
   for code quality and security. VIP strongly recommends [enabling required status checks](https://docs.wpvip.com/required-status-checks/)
   to ensure that no pull requests can be merged unless all issues detected by the
   Bot have been resolved where appropriate. 
 * **For Node.js applications**, the GitHub repository is initialized as a fork 
   of the [vip-go-node-skeleton](https://github.com/Automattic/vip-go-node-skeleton)
   repository. In its initial state, the repository of a Node.js application is 
   a useful example for the basic requirements necessary to successfully deploy 
   and run a Node.js application on VIP’s infrastructure. Detailed explanations 
   for the basic requirements can be reviewed in the code comments of [the entry point `/src/index.js`](https://github.com/Automattic/vip-go-node-skeleton/blob/trunk/src/index.js).
   This repository also includes [code examples](https://github.com/Automattic/vip-go-node-skeleton/blob/trunk/examples)
   that demonstrate how to use various frameworks and technologies on the VIP Platform.

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

Code in a wpcomvip GitHub repository only deploys to a VIP Platform environment 
when [the Default Deployment method](https://docs.wpvip.com/code-deployment/default-deployment/)
is enabled for the environment. Code developed in a version control system outside
of an application’s [wpcomvip GitHub repository](https://docs.wpvip.com/github-repository/)
can be deployed to the environment when [the Custom Deployment method](https://docs.wpvip.com/code-deployment/custom-deployment/)
is enabled.

A wpcomvip GitHub repository associated with [a customer organization](https://docs.wpvip.com/organization/)
can deploy to more than one of their [applications](https://docs.wpvip.com/application/).
[Create a VIP Support request](https://wordpressvip.zendesk.com/) if this configuration
is desired.

## Limitations

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](https://docs.github.com/en/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps)
   cannot be added to these repositories.
 * 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](https://docs.wpvip.com/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](https://docs.github.com/en/organizations/organizing-members-into-teams/about-teams).
The following VIP GitHub teams will appear in [a repository’s “Collaborators and teams” access list](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)
and must not be removed:

 * [VIP](https://github.com/orgs/wpcomvip/teams/vip)
 * [VIP (Read)](https://github.com/orgs/wpcomvip/teams/vip-read)
 * [VIP Temporary – vip-wordpress-com (Admin)](https://github.com/orgs/wpcomvip/teams/vip-temporary-vip-wordpress-com-admin)
 * [VIP Temporary – vip-wordpress-com (Read)](https://github.com/orgs/wpcomvip/teams/vip-temporary-vip-wordpress-com-read)

Last updated: February 25, 2026