GitHub Actions "Unable to interpret value as a boolean"
A key expecting a boolean got a value that is not true or false, often a quoted string or an empty expression result.
What this error means
The workflow fails with "Unable to interpret value as a 'boolean'" at a key such as continue-on-error or an input typed boolean.
github-actions
The workflow is not valid. .github/workflows/ci.yml (Line: 14): Unable to interpret value as a 'boolean': 'yes'Common causes
A non-boolean literal
Values like yes, no, or 1 are not booleans here; only true and false are accepted.
An expression returning a string
An expression that yields a quoted string instead of an actual boolean fails the type check.
How to fix it
Provide a real boolean
- Use unquoted true or false.
- For expressions, compare to produce a boolean, not a string.
.github/workflows/ci.yml
continue-on-error: ${{ github.ref != 'refs/heads/main' }}How to prevent it
- Avoid quoting boolean values in YAML.
- Run actionlint to catch boolean type mismatches.
Related guides
GitHub Actions "Invalid type" for env or with valuesFix the GitHub Actions "Invalid type" error for env or with values caused by passing a list or mapping where…
GitHub Actions "Invalid format" for timeout-minutesFix the GitHub Actions invalid format error for timeout-minutes caused by a non-numeric value or an expressio…
GitHub Actions "Context access might be invalid" (actionlint)Fix the actionlint warning "Context access might be invalid" for GitHub Actions caused by referencing a secre…