Add --gemfile flag to bundle pristine
#7353
Open
Conversation
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
segiddins
approved these changes
Jan 6, 2024
deivid-rodriguez
approved these changes
Jan 8, 2024
|
Planning to fix the tests soon. 😵💫 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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?
I just switched computers and my gems needed to be rebuilt. I first tried
bundle pristine --gemfile tool/bundler/vendor_gems.rband it didn't work.I ended up with
gem pristine --allbut it still seemed odd that the --gemfile flag didn't exist for pristine.What is your fix for the problem, implemented in this PR?
Add
--gemfiletobundle pristine.Make sure the following tasks are checked