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

Use same --exclude-limit as the existing .rubocop_todo.yml #618

Open
r7kamura opened this issue May 14, 2022 · 1 comment
Open

Use same --exclude-limit as the existing .rubocop_todo.yml #618

r7kamura opened this issue May 14, 2022 · 1 comment

Comments

@r7kamura
Copy link
Contributor

This is a feature request.

diff --git a/.rubocop_todo.yml b/.rubocop_todo.yml
index a52b2780619..5fb492fbe4e 100644
--- a/.rubocop_todo.yml
+++ b/.rubocop_todo.yml
@@ -1,469 +1,18 @@
 # This configuration was generated by
-# `rubocop --auto-gen-config --exclude-limit 99999`
+# `rubocop --auto-gen-config`
 # on 2022-05-14 02:17:42 UTC using RuboCop version 1.29.1.
 # The point is for the user to remove these configuration records

I know there is --exclude-limit option in rubocop_challenger go command, but I think it would be great if this gem automatically set the appropriate --exclude-limit option (99999 in the above example) from the existent .rubocop_todo.yml by default.

@ryz310
Copy link
Owner

ryz310 commented May 14, 2022

@r7kamura
Indeed. Will be supported soon.

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

No branches or pull requests

2 participants