Yep, this is what we do for some pipelines. Our YAML looks like this (slightly edited for clarity/brevity and removing internal implementation details) since plugins are always specified per-step
Hi @dht, a plugin needs to be applied to a particular step, so your YAML there won’t quite work. You’ll need to put the skip checkout plugin on a command step of some sort, or this’ll be rejected as an invalid pipeline definition.