-
Notifications
You must be signed in to change notification settings - Fork 167
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
[Resolves #9] Cleanup rubocop todo #8
Conversation
@jean-francois-labbe I'm generally a big fan of standards. I maintain the gem 'perx-rubocop` that is the one I usually use as default settings. Since you've been investing your time in this as well, do you have any issues with it? |
@rpbaltazar That's a really good idea, to ease contribution the code must comply with a standard. I'm used to |
@rpbaltazar One thing that would be nice is to fix the travis-ci config in order to have a Green CI status, it would reassure users and enable faster tests status analysis (today I need to go check why the status is Red), easier merge request approval. |
I’ll wrap up the rubocop and have it merged then. |
- Fixes CI runs: - One of the rails versions [had a bug](rails/rails#38137) and causes the CI to fail. I've moved it to the allowed failures. - I think we should deprecate these versions as they are EOL. => New ticket to be created - Fixes rubocop installation - I had not realized when I merged rubocop installation that I was breaking all CI (I'm sorry for the rushed decision). This fixes the dependencies and all CI should be passing. - Adds rubocop to github actions. All the rubocop failures will be fixed with #8
3a97c39
to
9adea7f
Compare
No description provided.