DEVELOPER TOOLS

GitHub Actions Workflow Validator

Check a pasted GitHub Actions workflow for YAML errors, missing job or step structure, and unresolved job dependencies.

LOCAL WORKFLOW CHECK

Validate workflow YAML

Browser-only

Workflow text is parsed locally. Commands and actions are never executed; repository secrets, permissions, action inputs, event payloads, and runtime behavior are not available to this check.

Paste a workflow document, including its name, event trigger, and jobs. Input limit: 500,000 characters.

Validation result

Warnings

Jobs

No jobs were parsed.

Your workflow stays in this browser. The checker does not execute commands or send the YAML to GitHub or NAB Tools.

GitHub Actions workflow validator guide

A GitHub Actions workflow uses YAML to declare events, jobs, dependencies, runners, and steps. The workflow name is optional; this validator checks common structural issues so a missing job field or broken dependency is easier to catch before a push.

The checks are intentionally local and conservative. A workflow can be valid YAML but still fail in GitHub because action inputs, expressions, permissions, runner images, repository settings, or secrets depend on context this page cannot inspect.

Check the workflow shape first

A workflow name is optional; the workflow needs one or more trigger events under on and a jobs mapping. Each job needs a runner or reusable-workflow configuration; ordinary jobs contain steps that use an action or run a shell command. The validator checks those familiar relationships and points out missing or malformed structures.

YAML parsing is only the first step. Indentation determines whether an item belongs to the trigger, a job, or a step. Use the parsed diagnostics to correct structural problems before reviewing behavior, and keep each workflow focused so permissions and execution order remain understandable.

Review dependencies and step intent

Jobs can depend on other jobs through needs. The validator reports references to missing job IDs and dependency cycles, which would leave jobs unschedulable. Even when the graph is structurally valid, review it against the execution order you intend. A job’s steps should identify an action with uses or a shell command with run, not silently leave the work unspecified.

A structural check cannot determine whether an action tag exists, whether an action input is correct, or whether an expression resolves to the value you expect. Pin third-party actions according to your security policy, review their source, scope permissions narrowly, and test workflow changes in a safe branch.

Keep execution and secrets out of the checker

The workflow text is parsed in your browser; its commands are never run and no repository is contacted. This means the page cannot see repository secrets, environment protection rules, branch policies, organization-level runners, reusable workflows in another repository, or the exact GitHub event payload.

Before merging, use GitHub’s workflow validation and CI feedback in the repository where the workflow will run. Inspect the event filters, concurrency rules, permissions, artifacts, and any deployment job independently. Never use a successful structural report as evidence that a workflow is safe to execute.

Frequently asked questions

Does this run the workflow or any shell command?

No. It only parses and checks the pasted YAML locally; action and shell contents are never executed.

Why can valid YAML still be an invalid workflow?

GitHub Actions adds required structure and context-specific rules beyond YAML syntax, including job, step, action-input, expression, and runner requirements.

Can it verify secrets or repository permissions?

No. Secrets, organization policies, environment approvals, and repository permissions are not available to this browser-only check.

Should I still test it in GitHub?

Yes. Use the target repository’s CI and GitHub validation because action versions, expressions, event payloads, and repository settings affect real execution.

Privacy note: this tool processes your data in your browser. Your inputs and files are not submitted to NAB Tools.