summaryrefslogtreecommitdiff
path: root/spec/support/artifice/vcr_cassettes/realworld/index.rubygems.org/info/windows-pr/GET/request
diff options
context:
space:
mode:
authorBundlerbot <bot@bundler.io>2019-11-08 20:42:13 +0000
committerBundlerbot <bot@bundler.io>2019-11-08 20:42:13 +0000
commit03e08a01e897a10e2b8143f59026443c0a7b5adc (patch)
tree0b25c0cfe16ab83e4095acfc69e59c72d9cd9591 /spec/support/artifice/vcr_cassettes/realworld/index.rubygems.org/info/windows-pr/GET/request
parent6f05c531177a6b85f03b8387afe61ed9324d6d37 (diff)
parentf821c754ba7b4048cb37141992a32daee1cd58e7 (diff)
downloadbundler-03e08a01e897a10e2b8143f59026443c0a7b5adc.tar.gz
Merge #6455
6455: [CLI::Gem] Add a --rubocop option r=deivid-rodriguez a=segiddins Based upon #6451. ### What was the end-user problem that led to this PR? The problem was I always have to remember how to add RuboCop to my Rakefile when I set up a new gem. ### What was your diagnosis of the problem? My diagnosis was that RuboCop has become enough of a community standard that it makes sense to offer it in `bundle gem`. ### What is your fix for the problem, implemented in this PR? My fix adds an option to `bundle gem` to add in RuboCop, in the same way options like `:coc`and `:mit` are handled. ### Why did you choose this fix out of the possible options? I chose this fix because it does not require bundler have an opinion on _how_ rubocop is configured. Co-authored-by: Samuel Giddins <segiddins@segiddins.me>
Diffstat (limited to 'spec/support/artifice/vcr_cassettes/realworld/index.rubygems.org/info/windows-pr/GET/request')
0 files changed, 0 insertions, 0 deletions