1
0
Fork 0

Merge pull request #9115 from PrinsFrank/clarify-comitting-lock-file

Docs: Move note about not committing lock file to correct section.
pull/9122/head
Jordi Boggiano 2020-08-11 09:49:14 +02:00 committed by GitHub
commit 70a56c73e3
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions

View File

@ -142,6 +142,9 @@ reinstalling the project you can feel confident the dependencies installed are
still working even if your dependencies released many new versions since then.
(See note below about using the `update` command.)
> **Note:** For libraries it is not necessary to commit the lock
> file, see also: [Libraries - Lock file](02-libraries.md#lock-file).
## Updating dependencies to their latest versions
As mentioned above, the `composer.lock` file prevents you from automatically getting
@ -165,9 +168,6 @@ If you only want to install, upgrade or remove one dependency, you can explicitl
php composer.phar update monolog/monolog [...]
```
> **Note:** For libraries it is not necessary to commit the lock
> file, see also: [Libraries - Lock file](02-libraries.md#lock-file).
## Packagist
[Packagist](https://packagist.org/) is the main Composer repository. A Composer