Skip to content
100% local

GitHub Actions workflow generator

Assemble a ready-to-use GitHub Actions workflow file from your triggers, language and steps.

Output

GitHub Actions workflow generator

Building a GitHub Actions workflow from scratch means remembering the exact YAML shape for triggers, matrix strategy, caching and permissions, then testing it by pushing and watching the run fail on a typo. This tool assembles a complete, ready-to-save workflow file from a set of options, so you can preview the result before it ever reaches .github/workflows.

Choose which events start the workflow — push, pull request, a cron schedule, or a manual workflow_dispatch run — and restrict push and pull request to specific branches or file paths. Pick a language (Node.js, Python, Go, Rust, Java, or a generic job with no setup step) and a version matrix; the generator wires up the matching setup action, dependency cache and install command, including npm, Yarn or pnpm for Node.js projects. Toggle test and build steps, set the GITHUB_TOKEN permissions, add a concurrency group that cancels superseded runs, and attach an upload-artifact step for build output.

The output is a single YAML file with a live tally of jobs, steps and lines so you can see the shape of the workflow as you adjust options. Leaving a trigger unchecked entirely returns a clear message rather than an invalid file, and an incomplete cron expression is caught before it reaches GitHub.

Everything runs locally in your browser — no repository details, secrets or code are sent anywhere. Copy the result, download it as a .txt file to rename and drop into .github/workflows, or send it to another tool's input to keep editing.

FAQ

Where do I put the generated file?
Save it as a .yml file inside .github/workflows/ in your repository — for example .github/workflows/ci.yml.
Can I combine multiple triggers, like push and a schedule?
Yes. Turn on as many triggers as you need; each one gets its own section under "on:" in the generated file.
What does the version matrix do?
Listing more than one version, or choosing all three operating systems, makes the generator add a "strategy: matrix" block so the job runs once per combination.
Why does the tool sometimes show an error instead of a file?
Only two cases block generation: no trigger selected at all, or a schedule turned on with a cron expression that is not five fields. Fix the option and the workflow appears again.
Is my repository or workflow configuration uploaded anywhere?
No. The workflow is assembled entirely in your browser from the options you choose — nothing is sent to a server.