[Fix #12865] require 'bundler'
if possible and rescue Bundler::GemfileNotFound
#12866
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.
Closes #12865
This PR improves upon #12826, which tried to
require 'bundler'
if it's available, we we reverted after #12846.The issue wasn't the attempt to require Bundler. It was that we were calling
Bundler.default_lockfile
, which raisesBundler::GemfileNotFound
when you're in a folder with noGemfile.lock
.I can't test this right now, so this is just "blind coding". Can you try it out, @AmShaegar13
Before submitting the PR make sure the following are checked:
[Fix #issue-number]
(if the related issue exists).master
(if not - rebase it).bundle exec rake default
. It executes all tests and runs RuboCop on its own code.{change_type}_{change_description}.md
if the new code introduces user-observable changes. See changelog entry format for details.