-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Request: CLI option for listing all the files rubocop plans to inspect #2179
Comments
Another use case for this would be simply check if you got your excludes right. :-) |
👍 This sounds like a great idea! |
Great idea, I like it too. |
I guess the name of the option can be |
Glad to see the enthusiasm 😄 #2184 |
Anyone used this with test suite parallelism to have multiple containers run a subset of rubocop file targets? Would love an example using bash (with travis), otherwise will just hack out my own and post it here for others who are looking for something like this |
Use case:
I'm using Circle CI for continuous integration, and it has a neat feature where you can split work over multiple machines and they'll be run in parallel. Here's a page from their docs explaining how to configure your build to split your tests across multiple machines: https://circleci.com/docs/parallel-manual-setup
If I had easy access to the list of files RuboCop is going to inspect (based on the default list + whatever is added in AllCops: Include) I could pipe that into a script like the bash script referenced in that page, and then split the work of inspecting code style across multiple machines.
What do you think? I'm happy to try and do it if you think it might be useful to other people than just me 😄
The text was updated successfully, but these errors were encountered: