We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
.rubocop
Use the .rubocop.yml config
.rubocop.yml
Is a directory @ io_fillbuf - fd:7 .rubocop /Users/joejuzl/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/rubocop-0.42.0/lib/rubocop/options.rb:38:in `readlines' /Users/joejuzl/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/rubocop-0.42.0/lib/rubocop/options.rb:38:in `args_from_file' /Users/joejuzl/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/rubocop-0.42.0/lib/rubocop/options.rb:19:in `parse' /Users/joejuzl/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/rubocop-0.42.0/lib/rubocop/cli.rb:24:in `run' /Users/joejuzl/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/rubocop-0.42.0/bin/rubocop:14:in `block in <top (required)>' /Users/joejuzl/.rbenv/versions/2.2.3/lib/ruby/2.2.0/benchmark.rb:303:in `realtime' /Users/joejuzl/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/rubocop-0.42.0/bin/rubocop:13:in `<top (required)>' /Users/joejuzl/.rbenv/versions/2.2.3/bin/rubocop:22:in `load' /Users/joejuzl/.rbenv/versions/2.2.3/bin/rubocop:22:in `<main>'
Run rubocop in a directory with a sub-directory named .rubocop.
$ rubocop -V 0.42.0
The text was updated successfully, but these errors were encountered:
[fixes rubocop#3423] checks if .rubocop is a file before parsing
134c0db
c7fafe2
[Fix rubocop#3423] Check if .rubocop is a file before trying to parse…
944b901
… it (rubocop#3424)
No branches or pull requests
Rubocop errors when there is a directory named
.rubocop
Expected behavior
Use the
.rubocop.yml
configActual behavior
Steps to reproduce the problem
Run rubocop in a directory with a sub-directory named
.rubocop
.RuboCop version
The text was updated successfully, but these errors were encountered: