Currently both the beta-env and prod env of VCT are deployed on master.
For prod env, maintainers deploy the tool manually, where for beta-env the deployment is done (based on cron job) and the beta-env is always synced with current master.

Now that we aim to make beta-VCT a dev playground, we should have 2 branches beta-master and master, and should encourage all devs/new folks to cut their branch from beta-master.

We're open to discussion around other git branching strategies as well, and will implement the one which satisfies all of our use-cases.
Feel free to pitch in here (in phab itself)