Ashwin Maroli

I think its more of a Git limitation than JekyllBot's. The result would be the same if the commits were squashed manually on the terminal. What JekyllBot could do is...

Fair point :+1:

> Maybe also add a comment to the PR letting the author/maintainers know that there are new conflicts that need to be resolved? That's a good idea. But I'm :-1:...

> I'd rather minimize a comment that handle all conflicts. Probably that's how the rest of team feels as well.. :+1:

@blakegearin Jekyll 3.9.0 doesn't *contain the said vulnerability*. It is flexible enough to allow users upgrade on their discretion. Users just need to run `gem update kramdown` or `bundle update...

*ProTip: The `_site` folder (or any destination directory) is autogenerated. Never put your stuff into it. Jekyll never reads it.* To resolve your issue: 1. Move `assets/` directory from `_site/`...

Nokogiri has released [`v1.10.9`](https://github.com/sparklemotion/nokogiri/releases/tag/v1.10.9)

Before it gets added to GitHub Pages' whitelist, we'd like to get feedback from the community if the plugin provides what is expected.

## Workarounds *Disclaimer: Both of the following are undocumented and may have side-effects* - **place the gem outside the `jekyll_plugins` group in the Gemfile.** ```diff - gem 'github-pages', group: :jekyll_plugins...

`jekyll-feed` or any other plugin will be automatically loaded by Jekyll if it is a `runtime_dependency` of your theme. Under regular circumstances, a solution to disable such automatic loading would...