-
Notifications
You must be signed in to change notification settings - Fork 9
Fix Rubocop violations #494
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I trust Rubocop made the right auto-correct changes. And the name changes looks good to me too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice one, @spencertransier 👍
LGTM. I'll wait for this one to land before I finally merge #489 to avoid conflicts on your side, so that I can also update the code according to the updated rules over there.
Thanks @iangmaia. Sounds good, I'm excited to have your PR merged! |
What does it do?
.rubocop_todo.yml
. I went through and removed a section from the todo file, ran Rubocop, then fixed any of the issues it found..rubocop_todo.yml
to get the latest status by runningbundle exec rubocop --regenerate-todo
Naming/VariableName
changes, I verified that those variables are only used internally by those actions and are not breaking changes for clients.Checklist before requesting a review
bundle exec rubocop
to test for code style violations and recommendationsspecs/*_spec.rb
) if applicablebundle exec rspec
to run the whole test suite and ensure all your tests passCHANGELOG.md
file to describe your changes under the appropriate existing###
subsection of the existing## Trunk
section.MIGRATION.md
file to describe how the changes will affect the migration from the previous major version and what the clients will need to change and consider.