-
-
Notifications
You must be signed in to change notification settings - Fork 39
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
4 RuboCop errors prevent git commit #78
Comments
Changes are purely for style purposes in accordance to rubocop.yml settings. These four changes now permit a git commit without skipping via SKIP=RuboCop. JacobEvelyn#78
Thanks for doing this! My Overcommit/Rubocop setup has been a bit broken recently because of sds/overcommit#315, so I've sadly gotten used to skipping validations. I really appreciate this change though! |
Changes are purely for style purposes in accordance to rubocop.yml settings. These four changes now permit a git commit without skipping via SKIP=RuboCop. JacobEvelyn#78
No problem. I had never used RuboCop or Overcommit before so it was a bit confusing. Apparently it only prevents a commit if one of the files has an error. This is why running RuboCop in the directory produced far more offenses. |
Disable mutable constants until we tackle frozen strings. Add new TrailingComma style configs. Fix various offenses. JacobEvelyn#78
Enable mutable constants and freeze constant strings adding required frozen strings comment. Add new TrailingComma style configs. Fix various offenses. JacobEvelyn#78
Fixed in #79. |
Current master has four RuboCop errors that prevent a git commit without skipping. These are not of great importance but I feel the change is beneficial if not for style then at least to prevent confusion while contributing.
The text was updated successfully, but these errors were encountered: