Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds a required Rubocop step to the Ruby workflow.
Rubocop accepts a configuration option for the target Ruby version, which, in our case, defaults to the lowest version number in
stytch.gemspec
.For now, I think we should run Rubocop just once on that minimum/target Ruby version. But if we have a reason to run it as part of the test matrix, I think that would be fine too.
Testing
bundle
(see thatrubocop
andrubocop-rspec
got installed)bundle exec rubocop
(should report no errors)I also put up a PR with an intentional linter error in #95 as an example.