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.
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.
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.
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.