Skip to content
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

Upgrade rubocop, motivated by CVE. #1939

Closed
wants to merge 2 commits into from
Closed

Conversation

xaviershay
Copy link
Member

Defaulted most new things to off, though tried to keep performance and linters.

Note that .rubocop_rspec_base doesn't 100% match up with rspec-dev because I was adding to it as we went along. Once these are all merged I'm planning to ensure they're all consistent.

@xaviershay
Copy link
Member Author

I don't know WTF is going on with the build but I don't think it's green on master.

@benoittgt
Copy link
Member

I tried to rebase you PR (master...benoittgt:upgrade-rubocop), test are ok on ruby 2.4.1p111 but Rubocop shows 399 offenses 😢

@benoittgt
Copy link
Member

Sadly I think we can close this PR. Rubocop will be updated in rspec-rails 4.

https://github.com/rspec/rspec-rails/pull/2071/files#diff-8b7db4d5cc4b8f6dc8feb7030baa2478R59

And as I mention, there is too much offenses too fix a probably a big conflict with 4-0-dev.

Sorry Xavier.

@JonRowe
Copy link
Member

JonRowe commented May 30, 2019

Closing in favour of the 4-0-dev changes.

@JonRowe JonRowe closed this May 30, 2019
@pirj pirj deleted the upgrade-rubocop branch March 12, 2020 09:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants