jekyll-watch | Jekyll site when a file changes | Plugin library

After a so many attempts to fix the tests, i finnaly find a solution, thanks you @fredrik*

Here is my workflow file:

There may be one culprit gem here but you will run into this problem again and again unless you fix your underlying approach.

Look at your gems environment; all gems are installed into one folder, regardless of the project you’re working on. So, if you have two projects with conflicting dependencies you will get this problem again.

There are tools, like RVM, which let you create environments for each project. So, each project has its own separate collection of gems and even distinct versions of Ruby if you need 2.7 in one project and 2.5 for another.

See "Easy way to setting Ruby Version Manager (RVM) on projects" for how to use RVM and create a gemset for each project.

Make sure you add the front matter tag(Two lines of three dashes ("-")). Like this:

If another bundle install didn't work, delete Gemfile.lock then try specifying the version for public_suffix in Gemfile like so:

It looks due to the latest update of faraday - a gem depended by github-pages.

Try this workaround temporarily.

1. Add the following line to your Gemfile.

   gem 'faraday', '~> 0'

2. Use command bundle update to update the gem(s) with Gemfile.

   You may see outputs below:

   Fetching faraday 0.17.3 (was 1.0.0)
   Installing faraday 0.17.3 (was 1.0.0)

   That means gem faraday in ./vendor/bundle has been updated to the latest compatible version with the github-pages.

   You can check the version history of faraday at this page on rubygems.org.

3. Try bundle exec jekyll again.

4. If it doesn't work yet, try bundle pristine.

An alternative would be to "use Jekyll in Windows with Docker" (from James Sturtevant)

That would take advantage of the Docker image jekyll/jekyll (see its README).

In your Gemfile, uncomment #gem "jekyll-theme-basically-basic" to read gem "jekyll-theme-basically-basic".

For some reasons, in your .gitlab-ci.yml, all the gem install ... are useless, and it's the bundle install that does the required job.

The root of the problem seems to be bundler. What operating system and Ruby version are you using? It may be a problem with old OpenSSL library, so you can not install bundler and everything after it.

If you are using jRuby (your gem list output tells so), your problem seems to be the same as described in link. And there is a solution as well.

Maybe you forgot to set 2.1.2 version of ruby as global? (rbenv set global 2.1.2)

The error you're seeing should just be a warning and shouldn't impact deployment. I'd double-check the netlify logs again and see if there's another error you can find.

The latest published version of jekyll-sass-converter still uses the sass gem. It looks like they haven't released a new version that uses sassc yet.

If you add the below to your Gemfile, and then run bundle install, Jekyll will pick up the version that uses sassc instead of sass and get you past the warning you see