Conversation
|
Great!! @bundlerbot r+ |
|
📌 Commit d3275e8 has been approved by |
…colby-swandale [CLI::Gem] Add a --rubocop option 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.
|
💔 Test failed - status-travis |
|
Oh, i didn't notice the failing specs |
|
I think this just needs a rebase? |
d3275e8 to
ea6d542
Compare
|
This looks like it's rebased with some other commits it shouldn't have. |
|
Nah I just need to rebase the other branch, I think |
|
Oh i didn't notice that this wasn't going into master. |
880d379 to
ea0a09b
Compare
|
Rebased |
lib/bundler/templates/newgem/VERSION
Outdated
| @@ -0,0 +1 @@ | |||
| 0.1.0 No newline at end of file | |||
There was a problem hiding this comment.
I thought it would be better to add a newline for EOF.
ea0a09b to
225c68e
Compare
|
☔ The latest upstream changes (presumably 225c68e) made this pull request unmergeable. Please resolve the merge conflicts. |
ea6d542 to
2df9564
Compare
|
@indirect r? |
|
looks good, @bundlerbot r+ |
|
📌 Commit 2df9564 has been approved by |
…indirect [CLI::Gem] Add a --rubocop option 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.
|
💔 Test failed - status-travis |
|
@bundlerbot retry |
…indirect [CLI::Gem] Add a --rubocop option 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.
|
💔 Test failed - status-travis |
|
@bundlerbot retry |
|
Only changes I made is pointing this PR to master, and adding some missing spaces to the CLI message. |
|
1.8.7 matrix entry failed, not sure why. I restarted it. |
| <%- end -%> | ||
| <%- if config[:rubocop] -%> | ||
| spec.add_development_dependency "rubocop" | ||
| <%- end -%> |
There was a problem hiding this comment.
Worth also to add rubocop-rspec if chosen test framework is rspec IMO
|
This is going to have to wait for bundler 2 to be released before we can merge it. For some reason the ruby parser in 1.8.7 is locking up in |
|
This should be ok to merge now. I can work on getting this over the line. |
|
@colby-swandale, are you still planning to wrap up this PR? I can follow up if you are very busy 👍. |
82faeba to
1d2d5b0
Compare
1d2d5b0 to
0448ad5
Compare
7373: Refactor new gem specs r=deivid-rodriguez a=deivid-rodriguez ### What was the end-user problem that led to this PR? The problem was that I rebased #6455 and I had trouble getting the specs to pass. ### What was your diagnosis of the problem? My diagnosis was that the new gemspecs could use a refactor. ### What is your fix for the problem, implemented in this PR? My fix is to refactor these specs so that they are easier to read and modify. Co-authored-by: David Rodríguez <deivid.rodriguez@riseup.net>
0448ad5 to
2210cad
Compare
2210cad to
f821c75
Compare
|
@colby-swandale Forgot to mention that I updated this PR and it should be finally ready, in case you want to have a look at it before merging. |
7373: Refactor new gem specs r=deivid-rodriguez a=deivid-rodriguez ### What was the end-user problem that led to this PR? The problem was that I rebased #6455 and I had trouble getting the specs to pass. ### What was your diagnosis of the problem? My diagnosis was that the new gemspecs could use a refactor. ### What is your fix for the problem, implemented in this PR? My fix is to refactor these specs so that they are easier to read and modify. Co-authored-by: David Rodríguez <deivid.rodriguez@riseup.net> (cherry picked from commit 6ceec55)
|
@bundlerbot merge |
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>
Build succeeded |
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 gemto add in RuboCop, in the same way options like:cocand:mitare 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.