-
Notifications
You must be signed in to change notification settings - Fork 101
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
Inherit Jekyll's rubocop config for consistency #65
Conversation
This PR is the result of adding inherit_gem:\n jekyll: .rubocop.yml to .rubocop.yml and running rubocop -a so that this project follows Jekyll core's coding styles for consistency like other core plugins. This way, as Jekyll's Ruby style changes, so too will this project's.
LGTM after a quick glance! @parkr Thoughts on this? Also, what's up with the failing builds? 😛 |
LGTM.
Failing build is caused by an annoying activesupport & html-pipeline
incompatibility with some Ruby versions. The Travis config here should be
overhauled, I think. Loosen `JEKYLL_VERSION=3.0.0` to `3.0` for starters.
|
What's left to do on this? Trigger a new build? (I tried by closing the PR ans reopening it but it didn't do the trick). |
If the tests are only failing on this branch, then we should update the Travis config here. :) |
Does #87 remove a block from this PR getting merged? |
Finished in 0.818618s, 20.7667 runs/s, 47.6413 assertions/s.
17 runs, 39 assertions, 0 failures, 0 errors, 0 skips /cc @jekyll/archives |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With passing tests,
It's always funny looking at code you wrote a long time ago 😛 @jekyllbot: merge +dev |
This PR is the result of adding
inherit_gem: jekyll: .rubocop.yml
to.rubocop.yml
and runningrubocop -a
so that this project follows Jekyll core's coding styles for consistency like other core plugins. This way, as Jekyll's Ruby style changes, so too will this project's.