Build a GitHub Actions workflow YAML — triggers, jobs and steps for Node, Python or deploy flows.
How to use this tool
Push, pull request, or a schedule cron — pick at least one.
Node or Python, with the version your project uses.
Steps appear only when ticked, in the standard order.
Commit as ci.yml; the workflow runs on the next matching event.
Formula & worked example
Workflow CI, Node 20, push + pull request triggers, test and build steps gives a YAML file with checkout, setup-node v4, npm ci, npm test and npm run build steps.
Limitations — read this before you rely on it
A starter CI workflow for one job on ubuntu-latest. Matrix builds, caching beyond npm, environments, secrets and deployment targets are not generated — the deploy step is an explicit placeholder, not a working deploy.
Frequently asked questions
Save it as .github/workflows/ci.yml in your repository and commit it; GitHub picks it up automatically.
Deployments need repository secrets and a target, which differ per project. The placeholder marks where your real deploy step belongs — never paste a secret into a generated file.
It installs exactly the versions in package-lock.json, which makes CI builds reproducible instead of drifting with latest versions.
Yes — enter a cron expression in the schedule field and the workflow gains a schedule trigger alongside push and pull request.
Yes. GitHub Actions runs on private repositories too, subject to your plan's included minutes.