Clarify bundle check behaviour in docs
#7613
Merged
Conversation
This file contains 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
andyw8
force-pushed
the
andyw8/clarify-bundle-check-behaviour
branch
from
12f2764
to
c438c6d
Compare
|
Thanks for the documentation update. To clarify, are you saying that if you run bundle check when the lockfile is outdated, it will update the lockfile using installed gems, if they are compatible? Maybe we could focus on that behavior in the docs, clarifying that an outdated lockfile will be resolved using installed gems if they satisfy the requirement. |
|
Thanks for the feedback, I've pushed an update. |
martinemde
approved these changes
Apr 29, 2024
deivid-rodriguez
approved these changes
Apr 29, 2024
|
Thank you! |
deivid-rodriguez
added a commit
that referenced
this pull request
Apr 30, 2024
…viour Clarify `bundle check` behaviour in docs (cherry picked from commit 3853db9)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
Closes #7587
What is your fix for the problem, implemented in this PR?
Update the docs.
Make sure the following tasks are checked