Commit Graph

7 Commits

Author SHA1 Message Date
Javi Martín
8d4d1b7e4b Don't run linters in Code Climate
We're now running the linters in github actions, and code climate
doesn't use the same versions of the gems or npm packages that we're
using in the application. For example, only a few limited rubocop
versions are available, and sometimes code climate breaks because our
rubocop version isn't compatible with theirs. Now we're also using a
version of stylelint they don't support.

All in all, the linters check in code climate isn't helpful at all
anymmore.
2024-07-04 16:50:51 +02:00
Javi Martín
8f1739cc6a Use Stylelint instead of SCSS Lint in Code Climate
We forgot to do so in commit e210682ac.
2024-07-04 16:50:51 +02:00
Javi Martín
d921eee30d Update Code Climate Rubocop version
Code Climate was failing to analyze our repo because their rubocop 1.31
doesn't support rubocop-capybara.

Since we're using rubocop 1.56.4 in our code, we're going to use
version 1.56.3 for Code Climate which, at the time of writing, is the
latest available version in Code Climate.
2024-03-18 14:54:46 +01:00
Javi Martín
e3a93ac083 Update Rubocop version used in Code Climate
Rubocop 0.74 doesn't work with Ruby 3.x, and so the Code Climate report
was failing.
2023-09-03 22:16:37 +02:00
Javi Martín
d20af1225c Use rubocop 0.74 with code climate
It looks like rubocop 0.75 isn't available yet on code climate, and
their default rubocop version isn't compatible with our configuration.
2019-10-23 16:28:03 +02:00
rgarcia
a72a062808 Exclude /vendor folder from Code Climate 2017-12-08 11:20:28 +01:00
Bertocq
02ca07deb6 Add .codeclimate.yml config file to enable multiple engines 2017-06-19 10:53:31 +02:00