Nazar

@Shinmera If you have access to Github's [Actions](https://github.com/features/actions) (and Github's [Package Registry](https://github.com/features/package-registry)) you should be able to get a good CI/CD pipeline in place without leaving Github

I see what you mean, hence your initial story stating VMs. What is the dependency tree you envision to trigger the build? On Wed, Sep 25, 2019 at 7:53 AM...

So I think this looks promising: https://docs.travis-ci.com/user/reference/osx/#macos-version https://docs.travis-ci.com/user/deployment/releases/

As for the triggers, could either go the "monorepo" route which would make dependency triggers a little easier to handle, but would be a change in the setup; or hook...

Thanks @adwam12, I ended up doing just that and here is some code in case anybody is looking for guidance: ```javascript const ENV = process.env.FUNCTIONS_EMULATOR ? 'dev' : 'prod' const...