Your site’s code will live within a repository (repo) in the WordPress.com VIP GitHub organization, which will be created when you get started on VIP Go. By default this repository will be private, but can be public if required.
There is no limit to how many GitHub users from your organization, development team, and any third party agency can access your repository. We are happy to give nominated users from your organization admin access to your repository, allowing you to manage users or application integrations with your GitHub repo. Alternatively you are welcome to contact us to add users to a repository, please send us their GitHub usernames and whether you want them to have
write access to the repo, and we will then add them as GitHub collaborators for that repository.
Once the repository is created, you can choose to use this for your development, or simply to push your work to it as a Git remote and use any existing infrastructure (e.g. Beanstalk, Bitbucket, etc.)
Developing in your Github Repo #
If you choose to develop in a separate repo before pushing to the VIP repo, here are a few things to consider:
- Just like on WordPress.com sites, the VIP team may occasionally need to push security/performance related hotfixes to the
wpcomviprepo. (We usually do these through PRs for greater visibility.) It’s important that you have a process in place that merges the changes back to your main development repo.
- It’s probably a good idea to have your development repo mirror the structure of
wpcomviprepo directly to minimize complexities when pushing/pulling between them. Similarly, it’s a good idea to sync all commits as well (instead of doing large batched commits).
- For external dependencies (e.g. plugins), you can use submodules or subtrees (although, note that private submodules are not supported).