This setting was introduced automatically by the aforementioned rubocop cop,which makes it impossible to publish to rubygems automatically from a Githubaction with an API key, since one would always need the second factor.
When Rubocop introduces new rules, existing code may violate them unknowingly.
That's why they are in a "pending" state initially and need to be enabled
explicitly:
```
The following cops were added to RuboCop, but are not configured. Please set
Enabled to either `true` or `false` in your `.rubocop.yml` file:
- Layout/SpaceAroundMethodCallOperator (0.82)
- Style/ExponentialNotation (0.82)
For more information: https://docs.rubocop.org/en/latest/versioning/
```
Since we never automatically let gem upgrade rubocop in this project, it is
safe to enable all pending cops globally. This way new cops are not silenced and
one has to deal with them when upgrading the dependency on Rubocop.
```
The following cops were added to RuboCop, but are not configured. Please set Enabled to either `true` or `false` in your `.rubocop.yml` file:
- Lint/RaiseException (0.81)
- Lint/StructNewOverride (0.81)
- Style/HashEachMethods (0.80)
- Style/HashTransformKeys (0.80)
- Style/HashTransformValues (0.80)
For more information: https://docs.rubocop.org/en/latest/versioning/
```
It reached EOL on 20th Jun 2018 and no longer receives patches.
* set required Ruby version to >= 2.3 in spec file
* set rubocop's TargetRubyVersion to 2.3 and fix all the offenses
* added help flag
* updated .travis.yml
* added the list of all use-case commands
* changed rubocop
* made the necessary minor changes in helplog method and changed rubocop
