Enable CircleCI builds for PRs from fork

[omerlh]

I disabled them now because it's insecure - people can trigger builds that push images, or expose information. Need to investigate and decide how it is best to enable it again to test also PRs from a fork.

[Yshayy]

You can define another trigger that is triggered by "pull request comment added" (it requires being repository owner/maintainer) for forks.

For extra protection, you can specify the codefresh.yaml of the master branch in the pipeline to prevent tinkering with the yaml file.

It's also possible to trigger a different pipeline that do the "promoting" of images on Dockerhub (from CF internal registry) and trigger it in another step via CF cli. (this pipeline can be completely private)

[omerlh]

All sound like a good suggestions :) Thanks!

[omerlh]

Look like Kubernetes CI Robot can help us with that by adding the ok to test command.