You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 5, 2025. It is now read-only.
Since a lot of the blt action will do a composer update, acsf:init can be overkill once executed. But when acsf is updated, the drush commands need to be run or the factory will not deploy the code.
if we add a drush only command, we can let composer deal with the update and make sure the proper files are in place
<targetname="acsf:init:drush"description="Refreshes the acsf settings and hook files.">
<echo>Executing initialization command for acsf module.</echo>
<drushcommand="acsf-init">
<optionname="include">"${docroot}/modules/contrib/acsf/acsf_init"</option>
</drush>
<echo>Please add acsf_init as a dependency for your installation profile to ensure that it remains enabled.</echo>
<echo>An example alias file for ACSF is located in /drush/site-aliases/example.acsf.aliases.drushrc.php.</echo>
</target>
The text was updated successfully, but these errors were encountered:
Since a lot of the blt action will do a composer update, acsf:init can be overkill once executed. But when acsf is updated, the drush commands need to be run or the factory will not deploy the code.
if we add a drush only command, we can let composer deal with the update and make sure the proper files are in place
The text was updated successfully, but these errors were encountered: