I'm looking into the option of replacing CodeClimate with Stickler. While I know we all will miss the lovely "Your method has 7 lines (exceeds 6 allowed)", the main benefit of Stickler, that it makes fixes on its own! So no more making a commit just to fix this missing whitespace at the end of the file... 👌

Anyway, let's give it a shot and see if it's better or not.

Discussion: https://discuss.redash.io/t/replace-codeclimate-with-sticklerci/3037

Neat! +1

After some additional thought I realized that while the autofix feature is really nice, it has the potential to create confusion for contributors:

1. They push some code.
2. Stickler fixes lint issues.
3. They try to push again and get an error (because remote changed).

At this point, if they aren't familiar with Git enough, they might get confused/frustrated. The value we get from the auto fixes doesn't seem to worth this friction point.

👋 Stickler.

I will still put some effort in either replacing CodeClimate with a less noisy tool or adjust its settings.

@arikfr It would be neat if Stickler would just use the new change suggestions instead of fixing the problems outright.

@jezdez actually this is what I was looking for initially. But couldn't find such a solution. It's possible that there is no API for this feature yet, because it's still in beta.

@arikfr Ah I forgot it's in beta, true. I'd be surprised if Stickler wouldn't use it once it's in GA.