-
Notifications
You must be signed in to change notification settings - Fork 149
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
Rubocop #132
Comments
So, historically... This I agree it'd be a good idea to try to re-add it, though. |
That's fine, I can understand that. These style guidelines do change with time- for several reasons, this can be quite sensible. Happy to take the hit to reintroduce things as I think we get several significant benefits from it. Coupled with dependabot, I can't see this situation replacing itself (also, my best guess is this author wasn't aware of the autocorrect, which massively reduces the maintenance burden). Will open a PR with rubocop changes. |
Totally agreed, just thought I'd contribute how we got here |
Re-introduce rubocop as per issue prometheus#132 and pin to a specific style guide used by GoCardless and open-sourced at gocardless/gc_ruboconfig. This should reduce the frequency that style guidelines change between versions.
Re-introduce rubocop as per issue prometheus#132 and pin to a specific style guide used by GoCardless and open-sourced at gocardless/gc_ruboconfig. This should reduce the frequency that style guidelines change between versions.
It's often a good idea in open-source projects to provide automated code linting. Rubocop is a great gem that does this for Ruby and is highly customisable.
Is there any reason we wouldn't add this to make it easier for people to create code-style consistent PRs?
The text was updated successfully, but these errors were encountered: