Steps required to reproduce the problem
- Add a custom script in the
scripts section of composer.json
- Run
composer normalize
Expected Result
Successfully normalized ./composer.json.
Updating lock file.
Loading composer repositories with package information
[...]
Actual Result
Successfully normalized ./composer.json.
Updating lock file.
A script named qa would override a Composer command and has been skipped
Loading composer repositories with package information
[...]
Not a big deal at all but is there any way to suppress these warnings? I am about to include composer-normalize into our CI process and team mates might think something is wrong when seeing those.
From what I see it's due to Composer's Application->doRun() running twice and the second time around the scripts have already been defined.
I am on Composer version 1.10.05 right now.
Steps required to reproduce the problem
scriptssection ofcomposer.jsoncomposer normalizeExpected Result
Actual Result
Not a big deal at all but is there any way to suppress these warnings? I am about to include
composer-normalizeinto our CI process and team mates might think something is wrong when seeing those.From what I see it's due to Composer's
Application->doRun()running twice and the second time around the scripts have already been defined.I am on Composer version 1.10.05 right now.