Each VIP Go environment tracks a specific branch of your repository. For example, the production environment will track the
master branch; if you have requested other sites they will each have a specific branch they are tracking.
If you have a child environment, the branch will always auto-deploy. For the production environment, the
master branch may be enabled with a GitHub Pull Request workflow which incorporates a review stage on pull requests. Merged pull requests and direct pushes are then deployed.
Deployment typically takes two to five minutes, but this time can vary depending on the size of your codebase and any additional Continuous Integration (CI) tasks that are configured for your environment.
Build and deploy
Code committed to your environment branches should contain all needed assets. On deploy, no additional building is done except for submodule includes. So if you are using composer, for example, you should commit code only after running
composer install, or consider using CI/CD automation to do that.
If you are using VIP’s available CI/CD (built branches) your changes in
master (once merged) will first be built in Travis or CircleCI and then pushed directly from there to your
master-built branch. The build code will then be deployed automatically.