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

Pin the rubocop version to prevent reactive fixing #8753

Merged
merged 1 commit into from Apr 3, 2017
Merged

Conversation

mfurtak
Copy link
Contributor

@mfurtak mfurtak commented Apr 3, 2017

Checklist

  • I've run bundle exec rspec from the root directory to see all new and existing tests pass
  • I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
  • I've read the Contribution Guidelines
  • I've updated the documentation if necessary.

Description

Because any new version of rubocop could introduce new rules, letting the version number float adds a lot of reactive fixing for us.

Pinning the version number will let us decide when we want to take on new style changes.

Because any new version of rubocop could
introduce new rules, letting the version
number float adds a lot of reactive fixing
for us.

Pinning the version number will let us
decide when we want to take on new style
changes.
@mfurtak mfurtak merged commit f617b2b into master Apr 3, 2017
@mfurtak mfurtak deleted the pin-rubocop branch April 3, 2017 15:01
Copy link
Member

@KrauseFx KrauseFx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a great idea, we should have done this earlier. I wish rubocop was at 1.0 already

@KrauseFx KrauseFx mentioned this pull request Apr 3, 2017
@fastlane-bot
Copy link

Congratulations! 🎉 This was released as part of fastlane 2.25.0 🚀

@fastlane fastlane locked and limited conversation to collaborators Jul 6, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants