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

Test against Jekyll 4.x #336

Merged
merged 3 commits into from
Mar 25, 2019
Merged

Test against Jekyll 4.x #336

merged 3 commits into from
Mar 25, 2019

Conversation

benbalter
Copy link
Collaborator

@benbalter benbalter commented Mar 22, 2019

Assuming tests pass, this PR will allow the plugin to be used with Jekyll 4.x.

I believe based on the blame, the Pages gem was only required to make local previewing of the documentation easier (but isn't necessary for the plugin itself, tests, etc.

@ashmaroli
Copy link
Member

The documentation for RuboCop's Lint/ToJSON cop notes that:

Since JSON#generate allows for an optional argument, your method should too.

I think that's reasonable.
But the question is, should that be done in this PR or a separate commit to master?

@DirtyF
Copy link
Member

DirtyF commented Mar 25, 2019

@jekyllbot: merge +dev

@jekyllbot jekyllbot merged commit 23ccab3 into master Mar 25, 2019
@jekyllbot jekyllbot deleted the jekyll-4-0 branch March 25, 2019 11:33
jekyllbot added a commit that referenced this pull request Mar 25, 2019
maveille pushed a commit to maveille/jekyll-seo-tag that referenced this pull request Aug 3, 2019
maveille pushed a commit to maveille/jekyll-seo-tag that referenced this pull request Aug 3, 2019
@jekyll jekyll locked and limited conversation to collaborators Mar 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants