Avoid Bundler deprecation warning by using 'bundle config set path'#9
Open
duckinator wants to merge 1 commit intoRubyElders:mainfrom
Open
Avoid Bundler deprecation warning by using 'bundle config set path'#9duckinator wants to merge 1 commit intoRubyElders:mainfrom
duckinator wants to merge 1 commit intoRubyElders:mainfrom
Conversation
From Bundler's output: > Using the config command without a subcommand [list, get, set, unset] is deprecated and will be removed in the future.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 should fix the problem where
rbcauses Bundler to emit deprecation warnings, due tobundle config KEY VALUEbeing deprecated in favor ofbundle config set KEY VALUE.A screenshot of what prompted this PR: