Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not a dependency of github-pages #9

Closed
mrmanc opened this issue Oct 30, 2018 · 2 comments
Closed

Not a dependency of github-pages #9

mrmanc opened this issue Oct 30, 2018 · 2 comments

Comments

@mrmanc
Copy link

mrmanc commented Oct 30, 2018

Describe the bug

I’ve just had to add jekyll-include-cache as an explicit gem in a site’s Gemfile, which feels odd as other plugins come in as dependencies of github-pages. https://help.github.com/articles/configuring-jekyll-plugins/ indicates that it is a supported plugin, and yet it doesn’t seem to be a dependency. Should https://pages.github.com/versions/ now show jekyll-include-cache as an available plugin?

Steps to reproduce the behavior

  1. Build a site with https://github.com/mmistakes/minimal-mistakes/ as the remote theme and no version set, with only the github-pages gem specified in the Gemfile.

Expected behavior

The site should build.

Instead you get an error stating:

Dependency Error: Yikes! It looks like you don't have jekyll-include-cache or one of its dependencies installed. In order to use Jekyll as currently configured, you'll need to install this gem. The full error message from Ruby is: 'cannot load such file -- jekyll-include-cache' If you run into trouble, you can find helpful resources at https://jekyllrb.com/help/!

… as reported here: mmistakes/minimal-mistakes#1875. I know this can be fixed by adding the plugin as a gem dependency but that doesn’t feel right if this is intended to be a supported GHP plugin.

@stale
Copy link

stale bot commented Dec 29, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Dec 29, 2018
@settings settings bot removed the wontfix label Jan 10, 2019
@stale
Copy link

stale bot commented Mar 11, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Mar 11, 2019
@stale stale bot closed this as completed Mar 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant