If you choose to develop in a separate repo before pushing to the VIP repo, here are a few things to consider:
- The VIP team may occasionally need to push security/performance related hotfixes to your
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 your
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).
- When syncing with pull requests, be sure to review these in GitHub for automated code scanning comments added by our automation that may be flagging possible PHPCS issues.
- For external dependencies (e.g. plugins), you can use submodules or subtrees (although, note that private submodules are not supported, and public submodules you do not control are discouraged).