name | about |
---|---|
Bug Report |
Report an issue with RuboCop you've discovered. |
Be clear, concise and precise in your description of the problem. Open an issue with a descriptive title and a summary in grammatically correct, complete sentences.
Use the template below when reporting bugs. Please, make sure that you're running the latest stable RuboCop and that the problem you're reporting hasn't been reported (and potentially fixed) already.
Before filing the ticket you should replace all text above the horizontal rule with your own words.
Describe here how you expected RuboCop to behave in this particular situation.
Describe here what actually happened.
Please use rubocop --debug
when pasting rubocop output as it contains additional information.
This is extremely important! Providing us with a reliable way to reproduce a problem will expedite its solution.
Include the output of rubocop -V
or bundle exec rubocop -V
if using Bundler.
If you see extension cop versions (e.g. rubocop-performance
, rubocop-rspec
, and others)
output by rubocop -V
, include them as well. Here's an example:
$ [bundle exec] rubocop -V
1.35.1 (using Parser 2.7.2.0, rubocop-ast 1.1.1, running on ruby 2.7.2) [x86_64-linux]
- rubocop-performance 1.9.1
- rubocop-rspec 2.0.0