Documenting allowing contrib modules for migration through composer lock file
This commit is contained in:
parent
a9f6861116
commit
2b6970929e
1 changed files with 7 additions and 1 deletions
8
.gitignore
vendored
8
.gitignore
vendored
|
@ -30,4 +30,10 @@ vendor/
|
||||||
.vagrant
|
.vagrant
|
||||||
|
|
||||||
## Ignore lock file during development / not used on platform anyway
|
## Ignore lock file during development / not used on platform anyway
|
||||||
composer.lock
|
## Temporarily allow deployment of select contrib modules (by permitting the lock file).
|
||||||
|
## So far we are using select contrib modules for migration only, which wouldn't
|
||||||
|
## technically ever be required on the platform... but they'd have to be uninstalled
|
||||||
|
## before the configuration were deployed. We need to at least report to sites "your
|
||||||
|
## composer.json/composer.lock file called for modules X and Y, which were not deployed"
|
||||||
|
## to make it easier to understand the resulting config import error :-/
|
||||||
|
# composer.lock
|
||||||
|
|
Loading…
Reference in a new issue