It’s complicated because we don’t do a checkout on your behalf when scheduling work I think there’s something in the pipeline for better monorepo support that might help here, but i don’t have an ETA What is it about the CI run on docs changes that you want to avoid?
basically everything: compiling binaries, tests, wasting lots of CircleCI resources ;)
Is this because of the concurrency limit, or because you have limited minutes, or just generally avoiding waste?
avoiding waste, thinking about the environment you know
There is a trick you can do to cut a job short early and mark it as passed. It’ll still run any dependent jobs, so you might want to wrap it up in a command and sprinkle it about your jobs:
circleci task halt
Thanks, this helped