At least on drone 1.0(latest RC), there are steps for which the default clone step is always executed, even if the step is not meant to be executed.
Lets say a drone config defines a pipeline for push events and another for pull_request events.
Both pipelines will execute the default clone step even though only one runs at a time.
For big projects, one might grow as big as 50 pipelines(this is a rough low estimate for one of our projects).
Drone knows which piipelines are involved before starting to run them or, how would the UI know what to show?
So, why not go as far as inspecting if a pipeline is suppose to run for the current event?
If its not supposed to run, don’t even clone.
And, as a feature request(suggestion), don’t even show steps on the UI which are not supposed to run.
Can you imagine going through 100+ pipelines, half of which are skipped and the other half runs?