GitHub Actions Generator

Generate valid .github/workflows/*.yml files from a visual form. Configure triggers, steps, matrix strategy, environment variables, secrets, and artifacts. No external dependencies - YAML generation is pure TypeScript.

Template di Workflow

Impostazioni Workflow

Trigger degli Eventi

Guida Rapida

Action Comuni

  • actions/checkout@v4 - Checkout del repository
  • actions/setup-node@v4 - Configura Node.js
  • actions/setup-java@v4 - Configura il JDK
  • actions/setup-python@v5 - Configura Python
  • actions/setup-go@v5 - Configura Go
  • actions/upload-artifact@v4 - Carica artifact
  • actions/download-artifact@v4 - Scarica artifact
  • docker/login-action@v3 - Login al registry Docker

Variabili di Contesto

  • $${{ github.sha }} - SHA del commit
  • $${{ github.ref }} - Riferimento branch/tag
  • $${{ github.actor }} - Utente che ha attivato il workflow
  • $${{ github.repository }} - owner/repo
  • $${{ secrets.NAME }} - Secret del repository
  • $${{ env.KEY }} - Variabile d'ambiente
  • $${{ matrix.os }} - OS corrente della matrix
  • $${{ runner.os }} - Nome del sistema operativo del runner

Esempi di Pianificazione Cron

  • 0 0 * * * - Ogni giorno a mezzanotte UTC
  • 0 9 * * 1-5 - Nei giorni feriali alle 09:00 UTC
  • */15 * * * * - Ogni 15 minuti
  • 0 0 1 * * - Il primo di ogni mese
  • 0 6,18 * * * - Due volte al giorno (06:00 e 18:00)

Come utilizzare Generatore Workflow GitHub Actions

Choose a starting template

Select Pipeline CI/CD, Only Test, Build and Push Docker, Deploy or Release: automatically sets up trigger and typical steps for that scenario.

Configure trigger, step and language

Activate triggers (push, pull request, schedule cron, manual dispatch), add a preset step for Node.js/Java/Python/Go or a custom step (action or shell command).

Add matrix, env/secrets and artifact (optional)

Enable matrix strategy to test on multiple OS versions, define environment variables (marking sensitive ones as secrets) and configure artifact upload/download.

Copy or download the YAML file

The YAML file updates live as you modify the configuration. Copy it to notes or download it ready to be saved in .github/workflows/.

Suggerimenti

  • Use actions/checkout@v4 and actions/setup-* for the most recent versions indicated by the tool, which are already pre-configured in presets.
  • Activate matrix strategy only when needed to test more combinations: increases minute consumption CI by proportion of number of combinations.
  • Check the bottom of the page for "Context Variables" block for references such as ${{github.sha}}, ${{secrets.NAME}} and similar to use in custom steps.

Domande frequenti

Where is the YAML file saved?

In the .github/workflows folder of your repository, with a .yml extension (e.g., .github/workflows/ci.yml), GitHub Actions automatically detects and runs any files in that folder based on the triggers you've configured.

How do I handle secrets (e.g. Docker Hub tokens) without exposing them in the workflow?

Mark the variable as "secret" in Env and Secrets section: the tool automatically generates a reference ${{ secrets.NOME_VARIABILE }} instead of the clear value. The actual secret value is then configured on GitHub in Settings > Secrets and variables > Actions, never committed to the repository.

What is the purpose of the Matrix Strategy?

Allows you to run the same job on multiple combinations of operating system and/or language version (e.g. Node 18/20/22 on Ubuntu and Windows) in parallel, so you can check compatibility without manually duplicating your workflow.

Does the generated YAML file have syntactic correctness for GitHub Actions?

The generator produces syntactically valid YAML following the official structure (on/jobs/steps) and handles string escaping, but does not perform full semantic validation against the GitHub Actions schema. It always verifies the workflow with a test push or using the integrated GitHub Actions editor.

Can I customize a step generated from the language preset?

Be concise — keep similar length. Each step preset (e.g., "npm ci", "mvn test") remains editable: you can change its name, command or "with" parameters after adding it, or add a custom action or run step for unmet needs.