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

restrict rubocop to 0.50.0 and set Ruby parser to 2.0 #283

Conversation

colby-swandale
Copy link
Member

This PR is a bit nitpicky, so feel free to close this. I noticed that in .travis.yml that ruby 2.0 is being tested. It would be great to set rubocop to match the lowest supported version so that Rubocop doesn't suggests a change that Ruby 2.0 doesn't support

@coveralls
Copy link

Coverage Status

Coverage increased (+0.02%) to 97.707% when pulling 917b333 on colby-swandale:colby/restrict-rubocop-parser into 3988bc5 on ruby:master.

5 similar comments
@coveralls
Copy link

Coverage Status

Coverage increased (+0.02%) to 97.707% when pulling 917b333 on colby-swandale:colby/restrict-rubocop-parser into 3988bc5 on ruby:master.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.02%) to 97.707% when pulling 917b333 on colby-swandale:colby/restrict-rubocop-parser into 3988bc5 on ruby:master.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.02%) to 97.707% when pulling 917b333 on colby-swandale:colby/restrict-rubocop-parser into 3988bc5 on ruby:master.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.02%) to 97.707% when pulling 917b333 on colby-swandale:colby/restrict-rubocop-parser into 3988bc5 on ruby:master.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.02%) to 97.707% when pulling 917b333 on colby-swandale:colby/restrict-rubocop-parser into 3988bc5 on ruby:master.

@colby-swandale colby-swandale deleted the colby/restrict-rubocop-parser branch November 17, 2018 02:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants