Refrain from using red color for successful output in terminal

Currently, pipenv uses red to output standard virtualenv creation outputs:

Creating a virtualenv for this project…
Pipfile: /app/Pipfile
Using /usr/local/bin/python (3.7.3) to create virtualenv…
⠏ Creating virtual environment...Already using interpreter /usr/local/bin/python
Using base prefix '/usr/local'
New python executable in /root/.local/share/virtualenvs/app-4PlAip0Q/bin/python
Installing setuptools, pip, wheel...
done.

✔ Successfully created virtual environment! 
Virtualenv location: /root/.local/share/virtualenvs/app-4PlAip0Q

In a large terminal log output, this makes it very difficult to quickly scan the log for [absence of] errors.

Could we perhaps use a more subdued color (eg blue, albeit not the dark blue that people complained about), or even the default terminal color, since these aren’t particularly critical information to begin with…

[wadewilliams]

Probably the first step would be to agree on a set of guidelines for what each color means and when they should be used.

Recommended guideline:

Use red for errors only.

[jxltom]

I think this is in Circle CI which has different output with windows or linux terminals. It doesn’t display colors correctly, but this still needs some enhancement for sure.