Using the example from here: https://woodpecker-ci.org/docs/usage/pipeline-syntax https://woodpecker-ci.org/docs/usage/pipeline-syntax The problem here is tha

Using the example from here: https://woodpecker-ci.org/docs/usage/pipeline-syntax https://woodpecker-ci.org/docs/usage/pipeline-syntax The problem here is that if you load this YAML, modify it in code, and write it back out, but use a library or language that doesn't keep the ordering of the two entries the same, they will run in the wrong order. As in their example: backend will be built, followed by frontend. Serially. Those are two different steps. If instead you loaded this file and saved it without keeping the dictionary ordering the same, it is possible that frontend would not get built before backend. To get what you want, you have to use the group option to group them together: https://woodpecker-ci.org/docs/usage/pipeline-syntax#group---parallel-execution https://woodpecker-ci.org/docs/usage/pipeline-syntax#group--... at which point frontend/backend would get run in parallel. Gitlab CI requires you to define your stages up-front, and tasks in the same stage all get executed at the same time. On Github CI all tasks get executed in parallel by default, unless you specify a needs dependency at which point it will run the steps as required to meet those needs requirements.