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

Option to ignore unrecognized cop / department #10627

Closed
fschwahn opened this issue May 12, 2022 · 1 comment · Fixed by #10630
Closed

Option to ignore unrecognized cop / department #10627

fschwahn opened this issue May 12, 2022 · 1 comment · Fixed by #10630

Comments

@fschwahn
Copy link

Is your feature request related to a problem? Please describe.

We are using githubs superlinter (https://github.com/github/super-linter) for linting in our projects. The superlinter sometimes lags behind the current rubocop version for a few weeks (eg. current latest release is from April 1st - there have been 6 new rubocop versions in that time).

However, developers update rubocop more often locally, and run into cops we might not want to enforce, so we update our central rubocop config to disable / tweak rules. However, now github superlinter fails because we include configuration which it doesn't understand yet due to being on an older version of rubocop.

Describe the solution you'd like

An option to opt-out of errors in case of unrecognized cops. The default could stay as is.

Describe alternatives you've considered

I though about disabling NewCops - but that's not really something we want to do, we just want to opt-out of cops which don't fit our use cases.

nobuyo added a commit to nobuyo/rubocop that referenced this issue May 13, 2022
…ps` to ignore any unknown cops or departments in .rubocop.yml
bbatsov pushed a commit that referenced this issue May 13, 2022
…ignore any unknown cops or departments in .rubocop.yml
@fschwahn
Copy link
Author

Oh wow, thanks. That was a quick turnaround - now I just have to get superlinter to pick up this option 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant