@@ -12,9 +12,13 @@ vendor directory.
1212
1313## Usage
1414
15- ` composer require drupal-composer/drupal-scaffold:dev-master ` in your composer
15+ Run ` composer require drupal-composer/drupal-scaffold:dev-master ` in your composer
1616project before installing or updating ` drupal/core ` .
1717
18+ Once drupal-scaffold is required by your project, it will automatically update
19+ your scaffold files whenever ` composer update ` changes the version of
20+ ` drupal/core ` installed.
21+
1822## Configuration
1923
2024You can configure the plugin with providing some settings in the ` extra ` section
@@ -90,6 +94,8 @@ specifically, from the most recent development .tar.gz archive). This might
9094not be what you want when using an old development version (e.g. when the
9195version is fixed via composer.lock). To avoid problems, always commit your
9296scaffold files to the repository any time that composer.lock is committed.
97+ Note that the correct scaffold files are retrieved when using a tagged release
98+ of ` drupal/core ` (recommended).
9399
94100## Custom command
95101
@@ -107,3 +113,9 @@ command callback to the `scripts`-section of your root `composer.json`, like thi
107113
108114After that you can manually download the scaffold files according to your
109115configuration by using ` composer drupal-scaffold ` .
116+
117+ Note that drupal-scaffold does not automatically run after ` composer install ` .
118+ It is assumed that the scaffold files will be committed to the repository, to
119+ ensure that the correct files are used on the CI server (see ** Limitation** ,
120+ above). After running ` composer install ` for the first time, also run
121+ ` composer drupal-scaffold ` , and commit the scaffold files to your repository.
0 commit comments