Composer 1.10.0 introduced a lock config option, which, when set to false will prevent a composer.lock file from being created and will ignore it when one exists.
This is a useful option for libraries such as this where the lock file has no meaning.
It also makes life easier for contributors as they don't have to remember that for this repo they should use composer update instead of composer install. Both will now work the same.
coverage: 96.408%. remained the same
when pulling c9de35f2d66c20d1d03276ae16799a8f493b9992 on JRF/composer-dont-write-lock-file
into 4019e27b32be21487b9a09c1b744f2f1e3368e03 on 1.x.
Composer 1.10.0 introduced a
lock
config option, which, when set tofalse
will prevent acomposer.lock
file from being created and will ignore it when one exists.This is a useful option for libraries such as this where the
lock
file has no meaning.It also makes life easier for contributors as they don't have to remember that for this repo they should use
composer update
instead ofcomposer install
. Both will now work the same.Refs: https://getcomposer.org/doc/06-config.md#lock