Comment by jakubadamw

I’ve always been annoyed with the sequential character of jobs in GitHub Actions – that it is impossible to run steps in parallel, when applicable, without moving the job’s logic away from the the .yaml constructs into, say, bash scripts. My ideal runtime for a CI workflow should in my view leverage the model of a DAG and the parallelism made plausible by that to the fullest. Depot CI seems to have addressed this quite well – https://depot.dev/docs/ci/how-to-guides/parallel-steps. I migrated a side project to use it now, and it’s working great – I am seeing some great speed-ups.