DevOps Generators

GitHub Actions Builder

All tools

Start a CI workflow from a preset and see which security choices it makes before you commit it.

How it works

Four simple steps

1

Pick a workflow preset

Start from Node, Docker, or Python CI templates.

2

Configure triggers

Set push/PR events, versions, cache, and matrix OS.

3

Read security lint

Catch risky permissions and pull_request_target patterns.

4

Copy workflow YAML

Save under .github/workflows in your repo.

GitHub Actions Builder

About GitHub Actions Builder

A repository has no CI yet, and you want a workflow that installs, builds and tests on every pull request without handing the job a write token it does not need. Writing that YAML from memory is where indentation slips and broad permissions creep in.

Three presets are available. Node CI runs npm ci and then lint, build and test with --if-present. Python upgrades pip, installs requirements.txt and runs pytest. Docker sets up QEMU and Buildx, logs in to GHCR with GITHUB_TOKEN, derives tags with docker/metadata-action and pushes, except on pull requests. You choose branches, the push, pull_request, workflow_dispatch and pull_request_target triggers, a language version or build platforms, the timeout, dependency caching, a concurrency group and, for Node or Python, an OS and version matrix.

The security lint fails the result if pull_request_target is ticked, and it always warns that actions are pinned to tags such as @v4 rather than commit SHAs. Take that warning seriously for anything touching secrets. The Docker preset also requests id-token: write even though no step uses OIDC yet, so remove it if you have no plans to. Before the Docker preset builds your image, run the file through the Dockerfile linter. Scheduled runs need a cron line you add yourself, and the cron expression generator helps with that.

The YAML is built in the page; nothing about your repository is fetched. Job secrets can be prepared with the Env Validator, which exports gh secret set commands.

Keyboard shortcut

Ctrl Enter - Run tool
FAQ

Frequently asked questions

See all FAQs

Answers for this tool. For site-wide help, open the FAQ hub.

The matrix replaces it. Node runs on 18, 20 and 22, and Python on 3.10 through 3.13, each across ubuntu-latest, macos-latest and windows-latest with fail-fast turned off. Trim the lists if you only support some of those.

Multi-architecture images are handled by Buildx instead. Choose linux/amd64 or linux/amd64,linux/arm64 as the platform, and QEMU emulates the other architecture during the build.

No. The push setting is tied to the event name, so pull request runs build the image to catch errors without publishing it. Other events, such as pushes to the listed branches, do publish.

View more FAQs

Related tools

View all

Kubernetes Manifest Studio

Generate Deployment, Service, and Ingress YAML with a drift checklist.

Open

K8s Inspector

Summarize Kubernetes YAML kinds, names, and labels.

Open

K8s Resource Diff

Diff two Kubernetes manifests locally.

Open

K8s Manifest Splitter

Split multi-document YAML into one file per resource.

Open

Explore 321 free tools

Everything you need as a developer, marketer or creator - in one beautiful place.

Browse all tools