Advertisement
Guide
About the GitHub Actions Builder
Workflows with several jobs are easier to read as a picture than as YAML: which jobs run in parallel, what waits for what, and where a deploy sits. Lay the jobs out on the canvas, draw the dependencies, and the builder writes the workflow file with the jobs in order and needs: filled in.
For a single CI job from a few questions, the GitHub Actions Generator is quicker. Nothing you enter leaves your browser.
How to use it
- 1Pick a template or add jobs with + Add node.
- 2Drag from the bottom dot of a job to another job to make the second wait for the first.
- 3Click a job to set its runner, condition, matrix and steps; click the background for triggers and permissions.
- 4Open the Code tab, then copy or download the file into .github/workflows/.
Frequently asked questions
What does an arrow mean?
An arrow from build to deploy adds needs: build to the deploy job, so it starts only after build succeeds. Jobs without incoming arrows start in parallel when the workflow runs.
Can I run a job even when one it needs failed?
Yes. Set its condition to always() or failure(). The Python template’s coverage report uses always() so it runs after every matrix leg.
Why are action versions not pinned to a commit?
Tags such as actions/checkout@v5 are what most projects use. For stricter supply-chain security, replace them with a full commit SHA after copying.