Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If the config file is included in the gem, then it will be applied to
users' site configurations alongside their own configuration.
This doesn't provide much benefit, since most of the configuration
options are either a) not applicable to users (e.g. the title setting),
or b) easily set by users to their own preferences (e.g. the markdown
settings).
Furthermore, some of the settings are actively harmful. In particular the
paginate
options are from the old
jekyll-paginate
. In recent versions ofJekyll, setting the old options causes build failures for users who are
using the newer
jekyll-paginate-v2
.Overall, I think it's useful to have
_config.yml
in the repository asan example, but I don't think we should ship it.