How to use the GitHub Actions Workflow Generator
- Pick your language, versions and branches.
- Choose triggers and the steps to run.
- Save the YAML as .github/workflows/ci.yml in your repository.
What does this tool do?
The generated workflow uses the official setup actions with dependency caching, runs a matrix when you list several versions or operating systems, and restricts the default token to read-only permissions. Optional jobs deploy a static site to GitHub Pages or push a Docker image to GHCR or Docker Hub after a green build.
Everything runs in your browser — nothing you paste is uploaded.
Why use it?
- Version and OS matrix.
- Least-privilege token.
- Optional deploy job.
Use cases
- Add CI to a new repository.
- Test against several language versions or operating systems.
- Deploy a static site to GitHub Pages after a green build.
What a CI workflow does
On every push and pull request to main, it checks out the code, sets up Node 20 and 22 in a matrix, restores the dependency cache, then runs lint, test and build. If any step fails, the commit gets a red ✗.
Common mistakes
- Giving the workflow token write permissions it doesn't need.
- No dependency caching, which makes every run slow.
- Putting secrets directly in YAML instead of repository secrets.
Privacy
Everything you type is processed in your browser. Nothing you enter is sent to our servers or stored by us. There's no account to create and nothing to install.
Frequently asked questions
Where does the file go?
.github/workflows/ci.yml in your repository.
What is a matrix?
A way to run the same job across several versions or systems in parallel.
Is it free?
Public repositories get free minutes; private ones have a monthly allowance.
Content last updated . See how M2Toolkit works.