In Drone 0.4, there were specific steps in the pipeline. Build, publish, deploy. In the event that someone forks your repo and submits the code back in an MR, the deploy step was not executed.
In Drone 0.8 due to the change to a pipeline, all steps are executed regardless. If someone is to commit onto the master branch of a fork of your code and submit it, the deployment step is executed - meaning code will end up in production without it actually stopping to be merged in.
In some instances, the YAML for Drone can be modified in an MR and executed - meaning that even if you do have a step with a limitation on branch, that YAML will still be read by drone and executed.
Has anyone any ideas how we can prevent certain steps from being executed in Drone during a fork and merge like we could in 0.4?