If your GitHub Pages repository contains a Sass or SCSS file with invalid content, your GitHub Pages site will not build.
If your GitHub Pages site fails to build because of invalid SCSS or Sass, you'll get an email that looks like this:
Subject: Page build failed
The page build failed with the following error:
Your SCSS file
example.scsshas an error on line 47: Invalid CSS after "...on: relative; }": expected selector or at-rule, was "}".
You will only receive an email if outbound email support is enabled on your Enterprise instance. For more information, contact your site administrator.
Troubleshooting SCSS or Sass
Tip: We strongly recommend running Jekyll locally so you can easily debug and fix build errors before pushing to your GitHub Enterprise instance. To learn more about troubleshooting options, see "Troubleshooting GitHub Pages builds."
- Reproduce the error by building your Jekyll site locally with the
- From the error described in the email, review the indicated line number.
- Install a Sass or SCSS linter for your favorite text editor to help you find errors before you publish.
Once you've fixed any Sass and SCSS errors, trigger another build on the server by committing and pushing your changes to your GitHub Pages repository.