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
Composer commands when used in CI, should always use the --no-interaction flag, which this action already (correctly) takes care of.
The heads-up:
After a recent discussion about this in the setup-php repo, a change has been made in setup-php to set the COMPOSER_NO_INTERACTION=1 flag (commit shivammathur/setup-php@e7e1eee), which will have the same effect for all composer commands run in a job.
This change is expected to be included in the next release of setup-php.
Impact on this action
I expect that this will/should probably not have any impact on this plugin, as users of this action may not necessarily be using the latest version of setup-php or may possibly not even be using setup-php.
@ramsey Either way, I figured it may be useful for you to know about this change in advance. Please feel free to close this issue if you agree that this upstream change will not impact this action.
The text was updated successfully, but these errors were encountered:
This is just a heads-up and for your information.
Basic premise:
Composer commands when used in CI, should always use the
--no-interaction
flag, which this action already (correctly) takes care of.The heads-up:
After a recent discussion about this in the
setup-php
repo, a change has been made insetup-php
to set theCOMPOSER_NO_INTERACTION=1
flag (commit shivammathur/setup-php@e7e1eee), which will have the same effect for all composer commands run in a job.This change is expected to be included in the next release of
setup-php
.Impact on this action
I expect that this will/should probably not have any impact on this plugin, as users of this action may not necessarily be using the latest version of
setup-php
or may possibly not even be usingsetup-php
.@ramsey Either way, I figured it may be useful for you to know about this change in advance. Please feel free to close this issue if you agree that this upstream change will not impact this action.
The text was updated successfully, but these errors were encountered: