Prevent direct rubocop CLI use

[saturnflyer]

A problem I've seen when moving to standardrb for one project is that people can still run bundle exec rubocop and they get some very scary looking output.

Switching to bundle exec standardrb gets us back to a happy place but this has come up often enough that I'm wondering if there's a way to either prevent it or inform people that using rubocop directly isn't supported.

I'm curious if anyone has thoughts or experience in managing the switch for existing projects.

[searls]

As wacky as it is, if we were to do this I am very confident we'd find out about a lot of teams either intentionally using rubocop to run Standard's rules or who have cause to run both Standard and RuboCop (which was more common before extend_config and plugins options, for instance running rubocop for only rspec/minitest and standard for the rest).

The only real idea I have might be to add a disable_rubocop_cli YAML option which would rely on us wrapping/overriding the CLI (If that's even possible, haven't had a reason to try something like that before) to help teams that are transitioning away from RuboCop from accidentally running it out of habit, as per your original question.

[saturnflyer]

Thanks. I figured that this is fraught with trouble, but I at least want to start the discussion.
Perhaps there's something I can learn about how others are handling an issue like this.

[pboling]

The experimental override is working for me, and results in gradual always running!

require:
  - rubocop/gradual/patch