Why are channels necessary?

[monfresh]

I couldn't find a clear explanation of why CodeClimate has to keep adding versions of Rubocop to the channels. Is it not possible to install the version of Rubocop that is specified in the Gemfile.lock and then analyze the PR using that version? It seems like CodeClimate is always behind in terms of adding the latest version of Rubocop to the channels.

If I don't specify the channel option in the .codeclimate config, it looks like CodeClimate uses version 0.52 of Rubocop. Why such an old version?

[monfresh]

Doing a quick search for alternatives in the GitHub Actions marketplace, I found reviewdog, and they offer the following options for setting the rubocop version, which sound very reasonable:

• empty or omit: install latest version
• gemfile: install version from Gemfile (Gemfile.lock should be presented, otherwise it will fallback to latest bundler version)
• version (e.g. 0.90.0): install said version

What is different about Code Climate that prevents it from having the Rubocop integration be this user-friendly? Would it not be a win-win for both the Code Climate team to not have to keep track of Rubocop releases and remember to manually add a new version of Rubocop to the channels, and for your customers to be happier and not have to wait for a particular version to be added to the channel?

[klyonrad]

channels are necessary because the codeclimate business does not prioritize appeasing the ruby dev ecosystem.

As I have written in an older comment I consider it the number one reason why I'd never advocate moving beyond the free plan for it.

The issue that you have written now is a

Duplicate of #93

[monfresh]

Thanks @klyonrad. I didn't see that issue! Maybe the more people make noise, the more they'll listen?