.NET — dotnet restore, dotnet test, dotnet build with the NuGet cache.
0
lines
0
bytes
0
steps
.github/workflows/ci.yml
About GitHub Actions Workflow Generator
Pick a trigger, choose your runner and toolchain, toggle caching and matrix builds, and get a ready .github/workflows/ci.yml you can drop into a repository. The output follows standard GitHub Actions idioms: checkout, setup- actions, dependency restore, and a lint/test/build phase.
Features
Push, pull_request, and workflow_dispatch triggers with branch selection,Node, Python, Java/Maven, Java/Gradle, Ruby, Go, and .NET toolchains,ubuntu, windows, and macos runners plus custom self-hosted labels,Optional cache with the correct path for each toolchain,Push, pull_request, and matrix support in one output
How to Use
1. Choose the trigger and target branches. 2. Select a runner and your toolchain. 3. Toggle caching and, if you want, a job matrix. 4. Copy the generated YAML into .github/workflows/ci.yml and commit.
Examples
A Node + ubuntu workflow with actions/setup-node v4, npm ci, npm test, npm run build, and caching. A Python + ubuntu workflow with setup-python, pip install -r requirements.txt, pytest, and pip cache. A Go workflow with setup-go and go test ./... with module cache.
Benefits
No more memorizing action versions and cache paths. Every generated workflow is self-contained, readable, and matches current GitHub Actions syntax.
Frequently Asked Questions
Is my configuration uploaded anywhere?
No. The generator is fully client-side: your branch, OS, and toolchain choices are combined into YAML locally and never sent to a server.
What file should this produce?
A .github/workflows/ci.yml file (or a custom name you type). Place it in the repository root; GitHub detects the file on push and runs the jobs automatically.
Which event triggers does it support?
push to branches, pull_request, and a manual workflow_dispatch trigger. You pick the branches and the generator writes the matching on: block.
Can I cache dependencies?
Yes. Enabling caching emits the actions/cache step tuned to the selected toolchain: npm, pip, Maven, Gradle, RubyGems, or Go module cache.
What runners are available?
ubuntu-latest, windows-latest, and macos-latest, with the ability to set a custom runner label for self-hosted setups.
Do I need a separate file per language?
No. The selected toolchain decides checkout, setup, dependency install, caching, and the lint/test/build commands all in one workflow.
Does it include a real Node or Python version of the generator?
No native code, no npm install. The tooling commands are emitted into YAML as steps, and the generator itself needs no build step.
Can I use it offline?
Yes. Once the page is served anywhere, it works offline like every other tool in this suite.