Error AtlasError Documentation and ResolutionGitHub documented errors
Browse documented GitHub errors with exact messages, troubleshooting context, and practical remediation steps.
Tool
GitHub Actions
GITHUB_ENV cannot be used to set the NODE_OPTIONS environment variableGitHub Actions blocks NODE_OPTIONS from being set through GITHUB_ENVconfiguration: GitHub Actions rejected an attempt to set NODE_OPTIONS through GITHUB_ENV because the runner blocks that environment variable for security reasons.
If your workflows use Docker container actions, job containers, or service containers, then you must use a Linux runnerGitHub Actions container job failed because the runner is not Linuxruntime: GitHub Actions container-based jobs and service containers require a Linux runner. Using macOS or Windows runners for these workflows causes the setup to fail.
Wrapping with double quotes (") will throw an errorGitHub Actions expression string used double quotes and failedconfiguration: GitHub Actions expressions treat double-quoted string literals as invalid in expression syntax, which can cause workflow validation or evaluation failures.
If you specify the access for any of these permissions, all of those that are not specified are set to `none`GitHub Actions GITHUB_TOKEN lost permissions because unspecified scopes were set to noneauthentication: GitHub Actions can unexpectedly lose needed GITHUB_TOKEN scopes when a workflow declares specific permissions, because all unspecified permissions are then set to none.
`!` is reserved notation in YAML formatGitHub Actions if expression starting with ! failed YAML parsingconfiguration: GitHub Actions conditionals that begin with ! must use expression syntax or quoting because raw YAML treats ! as reserved notation.
on.workflow_call.inputs.<input_id>.typeGitHub Actions reusable workflow input is missing a required typeconfiguration: GitHub Actions reusable workflow inputs must declare a type. If the type is missing or invalid, the workflow definition is not valid.
Subdirectories of the workflows directory are not supportedGitHub Actions reusable workflow is in an unsupported directoryconfiguration: GitHub Actions only recognizes reusable workflows in the repository's .github/workflows directory. Nested subdirectories are not valid for workflow files.
on.workflow_call.secrets.<secret_id>.requiredGitHub Actions reusable workflow is missing a required secretauthentication: GitHub Actions rejected a reusable workflow call because the called workflow declared a required secret that the caller did not pass.
For a workflow to be reusable, the values for `on` must include `workflow_call`GitHub Actions reusable workflow is missing workflow_callconfiguration: GitHub Actions cannot treat a workflow as reusable unless the called workflow explicitly declares the workflow_call trigger.
If a caller workflow passes an input that is not specified in the called workflow, this results in an error.GitHub Actions reusable workflow received an undeclared inputconfiguration: GitHub Actions rejected a reusable workflow call because the caller passed an input that the called workflow did not define under on.workflow_call.inputs.
You cannot use contexts or expressions in this keywordGitHub Actions reusable workflow uses does not allow contexts or expressionsconfiguration: GitHub Actions rejected a reusable workflow reference because jobs.<job_id>.uses must be a static workflow path and ref, not an expression-driven value.
Skip output `{output.Key}` since it may contain secretGitHub Actions skipped a job output because it may contain a secretconfiguration: GitHub Actions refused to send a job output because the runner detected it may include secret material and redacted it from downstream jobs.
Every step must define a `uses` or `run` keyGitHub Actions step is missing run or usesconfiguration: GitHub Actions could not validate the workflow because a step exists without either running a command or calling an action.
Invalid - creates a parse error that prevents your workflow from runningGitHub Actions workflow failed because a special pattern was not quotedconfiguration: GitHub Actions could not parse the workflow because a branch, tag, or path pattern beginning with special YAML characters was left unquoted.
Workflow file parse errorGitHub Actions workflow YAML is invalidconfiguration: GitHub Actions could not load the workflow because the YAML syntax is invalid, often due to unquoted special characters or malformed workflow structure.
workflow_dispatch only triggers workflows that exist on the default branchGitHub Actions workflow_dispatch did not work because the workflow is not on the default branchconfiguration: GitHub Actions manual workflow dispatch is only available when the workflow file exists on the repository's default branch, so branch-only workflow edits will not expose the manual run entry point.
Tool
GitHub Deployments
Tool
GitHub Pages
Missing docs folderGitHub Pages build failed because the docs folder is missingconfiguration: GitHub Pages could not publish the site because the repository is configured to build from the `docs` folder but that folder does not exist or is not in the expected branch.
Missing submoduleGitHub Pages failed because a referenced submodule is missingconfiguration: GitHub Pages could not build the site because a submodule referenced by the repository is missing or incomplete.
Tag not properly closedGitHub Pages failed because a tag was not properly closedbuild: GitHub Pages could not build the site because a Liquid or template tag was opened but not closed correctly.
Tag not properly terminatedGitHub Pages failed because a tag was not properly terminatedbuild: GitHub Pages could not build the site because a Liquid or template tag is malformed and does not terminate correctly.
Syntax error in 'for' loopGitHub Pages failed because of a Liquid for-loop syntax errorbuild: GitHub Pages could not build the site because a Liquid for-loop expression is malformed or uses unsupported syntax.
Markdown errorsGitHub Pages failed because of Markdown errorsbuild: GitHub Pages could not build the site because Markdown content contains syntax or formatting issues that break the Jekyll rendering process.
Relative permalinks configuredGitHub Pages failed because relative permalinks are configuredconfiguration: GitHub Pages could not build the site because the Jekyll configuration uses relative permalinks, which are not supported in the Pages build environment.
Invalid submoduleGitHub Pages failed because the submodule configuration is invalidconfiguration: GitHub Pages could not build the site because one of the configured Git submodules is invalid, broken, or inaccessible during the build.
Config file errorGitHub Pages failed with a Jekyll config file errorconfiguration: GitHub Pages could not build the Jekyll site because the `_config.yml` file contains invalid syntax or unsupported formatting.
Invalid YAML in data fileGitHub Pages Jekyll build failed because a data file contains invalid YAMLconfiguration: GitHub Pages could not build the Jekyll site because a file in the `_data` directory contains malformed YAML that Jekyll cannot parse.
Date is not a valid datetimeGitHub Pages Jekyll build failed because a date is not a valid datetimebuild errors: GitHub Pages could not build the Jekyll site because a page or post contains a date value that Jekyll cannot parse as a valid datetime.
File does not exist in includes directoryGitHub Pages Jekyll build failed because a file does not exist in the includes directorybuild errors: GitHub Pages could not build the Jekyll site because an `{% include %}` tag references a file that Jekyll cannot find in the `_includes` directory.
File is not properly UTF-8 encodedGitHub Pages Jekyll build failed because a file is not properly UTF-8 encodedbuild errors: GitHub Pages could not build the Jekyll site because one of the content or data files uses an encoding that Jekyll does not accept.
Invalid post dateGitHub Pages Jekyll build failed because a post has an invalid post datebuild errors: GitHub Pages could not build the Jekyll site because a post filename or front matter date does not meet Jekyll's post date expectations.
Invalid highlighter languageGitHub Pages Jekyll build failed because an invalid highlighter language was usedbuild errors: GitHub Pages could not build the Jekyll site because a code block or highlighting configuration references a language that the site highlighter does not recognize.
Invalid Sass or SCSSGitHub Pages Jekyll build failed because Sass or SCSS is invalidbuild errors: GitHub Pages could not build the Jekyll site because a Sass or SCSS stylesheet contains syntax errors that prevent preprocessing.
Unknown tag errorGitHub Pages Jekyll build failed with an unknown tag errorbuild errors: GitHub Pages could not build the Jekyll site because Liquid or Jekyll encountered a tag that is unsupported, misspelled, or not available in the Pages build environment.