jekyll: `Invalid theme folder: _sass` when using Github Pages with remote_theme
My Environment
| Software | Version(s) |
|---|---|
| Operating System | tested on macOS 10.14 and Ubuntu Linux thru circleci/ruby:2.4.1 |
jekyll |
Latest (v3.8.5) |
github-pages |
Latest (v198, just released yesterday) |
Jekyll-remote-theme |
Latest (v0.3.1) |
Expected Behaviour
A normal build without the warning: Invalid theme folder: _sass.
Current Behavior
Hi, we have a Jekyll theme build for our own Jekyll sites on a separate repo accessed thru jekyll-remote-theme and all have been working just fine until yesterday that we upgraded from v3.7.4 to v3.8.5 (based on the Github pages-gem v198 release).
When using Jekyll v3.8.x, there is a warning showing us: Invalid theme folder: _sass, this warning goes away if Jekyll is downgraded to v3.7.4.
The warning isn’t affecting us because the /_sass folder does exists on the Jekyll theme repo and all SCSS files are precompiled just fine. We think that this warning is telling us that the /_sass folder doesn’t exist on the main repo but that it’s expected and it shouldn’t produce any warning.
What do you suggest?
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 2
- Comments: 15 (12 by maintainers)
Commits related to this issue
- Adds Jekyll remote theme configuration, removes local theme configuration Note that local builds now throw invalid warnings as noted in: https://github.com/jekyll/jekyll/issues/7630 — committed to opendistro/for-elasticsearch-docs by aetter 5 years ago
- start using _sass folder to appease jekyll 3.8 warning see jekyll/jekyll#7630 — committed to ellemenno/programming-pages by ellemenno 5 years ago
- Update msg when theme subfolder is not available Fixes https://github.com/jekyll/jekyll/issues/7630 — committed to grupopv/jekyll by cetinajero 5 years ago
- Change the log-level for the log output message to debug. This change is proposed since the log output it is not actionable for the end-user. Fixes #7630 — committed to grupopv/jekyll by cetinajero 5 years ago
- Change the log-level for the log output message to debug. This change is proposed since the log output it is not actionable for the end-user. Fixes #7630 — committed to grupopv/jekyll by cetinajero 5 years ago
@ashmaroli Than you, I agree; the warning is confusing. It implies there is something that needs correcting.
I’ve just encountered this after upgrading to jekyll 3.8 (via github-pages 198), for a theme that does not have a
_sassfolder.Why is this a warning? What consequence is there for not including a
_sassfolder in a theme?