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

CodeClimate is not working #439

Open
sobrinho opened this issue Jul 19, 2022 · 5 comments
Open

CodeClimate is not working #439

sobrinho opened this issue Jul 19, 2022 · 5 comments

Comments

@sobrinho
Copy link

Isn't this plugin working anymore?

Running the standard in my project I can see the errors but CodeClimate isn't reporting anything:

Screen Shot 2022-07-19 at 18 03 28

cc @jakeonfire

@searls
Copy link
Contributor

searls commented Jul 19, 2022

Great question! I don't think I've used the plugin myself. It looks like it's passing in your screenshot, should it have failed?

@jakeonfire
Copy link

fwiw the plugin is hosted here: https://github.com/jakeonfire/codeclimate-standard, though @codeclimate manages the releases. it still works for us. there is no output from standard in that view ever. codeclimate will only scan files with changes and then only show you issues for code which you've changed. you can try the beta release (i'm not sure if it's different or not though).

version: "2"
plugins:
  standard:
    enabled: true
    channel: beta

@sobrinho
Copy link
Author

I'm using the beta channel and yes, I was expecting to see offenses there and as you can see there isn't a View output button there.

I will try again later today and report back.

@sobrinho
Copy link
Author

BTW, I tried to use the rubocop plugin alone and also together with the standard plugin but then it complains that the YAML from the gem couldn't be found, I'm guessing that's not how CodeClimate works (pulling my Gemfile somehow).

Which also makes me wonder, how the plugin knows the standard version I'm using in my project? Does it know at all?

@jakeonfire
Copy link

jakeonfire commented Jul 20, 2022

the plugin has its own Gemfile and Gemfile.lock so it's using 1.4.0 - a bit behind.

we are successfully using both rubocop and standard:

version: "2"
plugins:
  rubocop:
    enabled: true
    channel: rubocop-1-18-3
  standard:
    enabled: true
    channel: beta

not sure what you mean by

it complains that the YAML from the gem couldn't be found.

do you have a .rubocop.yml config file?

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

3 participants