Added ability to save original Gemfile.lock #22
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.
I understand that this probably will never be merged to master, so it's more like "feature request"
It also requires refinements, proper tests, etc… I'll work on that if you'll say that this feature may be merged once it's ready and stable.
The main idea here is to keep
Gemfile.lock
"pristine" when working using gem overrides. Ifbundler_inject.enable_pristine
option set to true this creates anotherGemfile.lock.local
near original one and uses it by default. So you don't need to remove overrides each time you want to commit changes.What do you think?