GitHub Actions Workflow Editor

Edit and validate GitHub Actions workflow YAML.

Valid YAML. Loading the workflow schema…

About the GitHub Actions Workflow Editor

Paste a workflow file, or start from the build-and-test starter, and edit it as YAML with syntax highlighting and line numbers, or switch to the Visual tab and build it as a form: jobs, steps, triggers, permissions and environment variables, with cron schedules glossed in plain English. Both tabs edit the same document, so comments, key order and any key the form does not cover stay exactly as written. YAML parse errors are reported with the line that failed, and every key is checked against SchemaStore's GitHub Actions workflow schema, so a misspelled runs-on or an unknown event shows up before a push does. An untouched file exports byte for byte. Drafts stay in this browser; nothing is uploaded.

How to use the GitHub Actions Workflow Editor

  1. Paste your workflow YAML into the editor, or press Starter to load a build-and-test example.
  2. Switch to the Visual tab to add, rename, reorder or remove jobs and steps, and to set triggers, permissions and env; switch back to Code to see the YAML it wrote.
  3. Fix any parse error shown in red under the editor; it names the line that failed.
  4. Read the schema warnings, each with a line number and the key it concerns, and correct the ones that matter.
  5. Press Copy, or Download to save the file as workflow.yml.
  6. Press Clear to empty the editor, or Clear draft to go back to the starter.

Frequently asked questions

Does this editor need access to my GitHub repository?
No. It never talks to GitHub. There is no login, no API call, and no upload. The YAML is parsed and checked in your browser tab, and drafts are stored only in this browser's local storage.
What is the difference between a parse error and a schema warning?
A parse error means the YAML itself does not parse, so GitHub could not read the file either; Copy and Download are disabled until it is fixed. A warning means the YAML parses but something does not match the workflow schema, such as an unknown key or a missing runs-on. Warnings never block export, because the schema occasionally lags behind new GitHub features.
Which schema are workflows checked against?
The community-maintained github-workflow.json from SchemaStore, the same schema YAML language servers use to validate these files in editors. A copy is bundled with the tool and loaded only on this page.
Does the Visual tab rewrite my YAML?
No. It edits the same document the Code tab shows, one key at a time. Comments, key order and anything the form does not model, such as matrix, services or container, stay as written and appear in a read-only Advanced block on the job or step that owns them. While the YAML does not parse, the Visual tab is disabled and the reason is shown next to it.
Will the editor reformat my YAML?
No. It edits the text directly, so comments, blank lines, quoting, and key order all survive, and an untouched document exports exactly as it was pasted. Tab inserts two spaces rather than a tab character, which YAML forbids for indentation.
Where is my draft stored?
In this browser's local storage, so the workflow is still there when you come back to the page. Clear draft removes it and reloads the starter, and Clear empties the editor, which removes it too.

Related tools