Skip to main content
PProfileMatch
← Path

CI/CD · CI/CD Build, Test and Artifact Stages with GitHub Actions

0 XP
  1. 1 current stop: learning
  2. 2 upcoming
  3. 3 upcoming
  4. 4 upcoming
  5. 5 upcoming

Finish after stop 5

Stop 1 of 5 · Assembly line gate

Trick to keep in mind+3 XP

No needs, no queue: jobs start in parallel. needs = wait for that job to pass.

In GitHub Actions, jobs run side by side unless you chain them. The needs key says a job must wait until the named job has finished successfully, and it is purely about ordering. It does not copy files across, merge machines or share caches. Every job still starts on its own clean runner.

Read it once, then a question tests whether the trick stuck.