Restore change to copy global with/without config locally upon bundle install
#4154
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.
What was the end-user or developer problem that led to this PR?
Turns out #3666, which I thought was a bug fix, broke things for some people.
The problem is that people are righteously assuming that
bundle config
should save configuration locally to the application, but currently it doesn't work like that.This "feature" of
bundle install
automatically copying globalwith
andwithout
configuration to the local configuration was creating the false impression thatbundle config
worked as you would expect and keeping people's expectations working.What is your fix for the problem, implemented in this PR?
I considered just making the switch and changing
bundle config
to be local but a few examples come up that could break because of doing that, so for the time being I'm just going to revert the change and release a patch release with the revert.Fixes #4142.
Make sure the following tasks are checked