Skip to content

Commit f123788

Browse files
Merge pull request #7613 from andyw8/andyw8/clarify-bundle-check-behaviour
Clarify `bundle check` behaviour in docs (cherry picked from commit 3853db9)
1 parent c933ecc commit f123788

File tree

2 files changed

+5
-0
lines changed

2 files changed

+5
-0
lines changed

bundler/lib/bundler/man/bundle-check.1

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,8 @@
99
\fBcheck\fR searches the local machine for each of the gems requested in the Gemfile\. If all gems are found, Bundler prints a success message and exits with a status of 0\.
1010
.P
1111
If not, the first missing gem is listed and Bundler exits status 1\.
12+
.P
13+
If the lockfile needs to be updated then it will be resolved using the gems installed on the local machine, if they satisfy the requirements\.
1214
.SH "OPTIONS"
1315
.TP
1416
\fB\-\-dry\-run\fR

bundler/lib/bundler/man/bundle-check.1.ronn

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,9 @@ a status of 0.
1515

1616
If not, the first missing gem is listed and Bundler exits status 1.
1717

18+
If the lockfile needs to be updated then it will be resolved using the gems
19+
installed on the local machine, if they satisfy the requirements.
20+
1821
## OPTIONS
1922

2023
* `--dry-run`:

0 commit comments

Comments
 (0)