-
-
Notifications
You must be signed in to change notification settings - Fork 271
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
Fix InternalAffairs/ExampleDescription
offenses on master
#1154
Conversation
9678924
to
6879ad6
Compare
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.
Thank you so much!
Diversity in example descriptions was triggering my OCD for so long.
6879ad6
to
f7d1953
Compare
@pirj Fixed as per your review comments. |
f7d1953
to
7f11e75
Compare
Could you please add to the PR description a link to the change in rubocop/rubocop that prompted these changes? |
7f11e75
to
dd40ff8
Compare
@bquorning Added |
Please ping us when your other PRs builds pass. |
CI is failing with latest rubocop https://app.circleci.com/pipelines/github/rubocop/rubocop-rspec/887/workflows/cb3ac5d9-a753-42fd-a26d-86b9e5bd8c69/jobs/20828
Rubocop change: rubocop/rubocop#9797 - Released in rubocop
v1.15.0
Before submitting the PR make sure the following are checked:
master
(if not - rebase it).CHANGELOG.md
if the new code introduces user-observable changes.bundle exec rake
) passes (be sure to run this locally, since it may produce updated documentation that you will need to commit).If you have created a new cop:
config/default.yml
.Enabled: pending
inconfig/default.yml
.VersionAdded
indefault/config.yml
to the next minor version.If you have modified an existing cop's configuration options:
VersionChanged
inconfig/default.yml
to the next major version.