-
Notifications
You must be signed in to change notification settings - Fork 13
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
Add Rubocop to Github CI #117
base: main
Are you sure you want to change the base?
Conversation
…t as we clean things up.
breeds = [ 'Labrador', 'Poodle', 'German Shepherd', 'Golden Retriever', 'Pug' ] | ||
weights = [ 'Small', 'Medium', 'Large' ] | ||
sexs = [ 'Male', 'Female' ] | ||
names = %w[Bella Buddy Buster Cali Charlie Max Oliver Oscar Penny Riley Shadow |
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.
<3
git_source(:github) { |repo| "https://github.com/#{repo}.git" } | ||
|
||
ruby "3.0.2" | ||
ruby '3.0.2' |
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 generally like to minimize the number of diffs when we're introducing rubocop to a repo at first. If we want to go with single quotes, we can create a PR afterwards that introduces that single rule change so that reviewing the diff is very simple.
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.
🚀
For issue #113
I added some Ignore rules just to get the Rubocop config file in place - we can tighten these restrictions as we work on things.
There are a number of manual changes I had to do in order to satisfy some of the rules - I wouldn't mind some eyes on those changes to make sure I didn't break anything. I'm mostly leaning on unit tests and CI here.