Download the PHP package slam/alert-on-composerlock-change without Composer
On this page you can find all versions of the php package slam/alert-on-composerlock-change. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download slam/alert-on-composerlock-change
More information about slam/alert-on-composerlock-change
Files in slam/alert-on-composerlock-change
Package alert-on-composerlock-change
Short Description Composer plugin that alerts (in dev) that composer.lock changed and so the developer should run `composer install`
License MIT
Informations about the package alert-on-composerlock-change
Alert on composer.lock change...
...when commanding a git pull
, git checkout
or a git merge
Show an alert when composer.lock
changed while moving between commits.
Installation
To use this extension, require it in Composer:
WARNING: git hooks overridden !
To enable the warning both .git/hooks/post-merge
and .git/hooks/post-checkout
are overridden.
Where to use it
This is useful in development, you clone the repo and you'll automatically
notified on composer.lock
changes without custom hooks/code (after the
first composer install
of course).
The alert is triggered also while moving between commits with git checkout
.
Where NOT to use it
You should avoid relying on this in production, as you are supposed to have a
dedicated strategy for deploy that involves much more than a plain git pull
.
Also this isn't useful for a library, as libraries shouldn't commit the composer.lock
.
Why not just run composer install
?
This is intended to help developers be aware of what happened in the repo while they where sleeping (uh?). Developers are supposed to investigate how the dependencies changed, to be aware of them and, if needed, to discuss the changes and improve them. If everything happens under the hood, knowledge would be much slower to gain.
All versions of alert-on-composerlock-change with dependencies
composer-plugin-api Version ^1.0.0