Output of setup:static-content:deploy contains red color, should be a friendlier color

[hostep]

Preconditions

1. macOS 10.12.6
2. iTerm2 3.1.5 with Solarized Dark theme
3. Magento 2.2.1
4. PHP 7.0.25

Steps to reproduce

1. Setup a fresh Magento 2.2.1 installation
2. Execute: bin/magento setup:static-content:deploy -f --theme Magento/blank en_US

Expected result

1. Output with friendly colors that don't give the impression that something went wrong

Actual result

1. Seeing a bunch of red colors on the screen, which makes you think something went wrong.
   

Discussion

I actually didn't notice this when working locally, but when deploying to a server. We see in the output of our deployment scripts a bunch of red colors, which almost always means something is going terribly wrong, but when looking closer at the output, it was just telling us what strategy is being used and how long it took.
I would suggest changing this color to something more friendly, like blue or green for example.
I don't know if there are some kind of Magento standards for the colors being used in the output of cli commands?

[magento-engcom-team]

@hostep, thank you for your report.
This seems to be correct Magento behavior. Please refer to the Community Forums or the Magento Stack Exchange site for advice or general discussion about this.
Otherwise you may submit Pull Request with the suggested changes.

[hostep]

Ok ...

I'm willing to submit a PR to fix this, but I need some feedback regarding if there is some kind of standard or policy for what colors we can use in what cases on the cli.

@magento-engcom-team: if you can provide some suggestions, that would be appreciated :)

[ihor-sviziev]

It was also not clear for me why it red, I was thinking there is an error somewhere. I think would be better replace with green color

[magento-engcom-team]

Hi @hostep. Thank you for the report. We are moving your feature request to the special project. You can track this issue here: magento/community-features#15

[magento-engcom-team]

Hi @hostep. Thank you for your report.
The issue has been fixed in #13709 by @hostep in 2.2-develop branch
Related commit(s):

• d5490144c5d833827ac37ae6f7cc53c6ff4182ac
• 3733deada21670bd45626a91786b601994ec08e2

The fix will be available with the upcoming 2.2.4 release.