I think implementing --color={auto|never|always} would in my mind also require detection if the current output destination actually supports color. For this PR I'd like to concentrate on the bare minimum - supporting the environment variable with correct precedence according to the spec.

Originally posted by @klaernie in #429 (comment)

Please open the thread for more information about the need and ideas

I feel like the following should be considered

• --color would be equivalent to --color=auto
• --no-color would be equivalent to --color=never, and might be reported as deprecated
• --color=always is unaffected by NO_COLOR=1
• --color=auto, and --color: enable color if the terminal supports it or we run in a CI environment that supports color (like GitHub Actions does). Disable color if $NO_COLOR is in effect.
• --color=auto and --color=always are discarded by NO_COLOR=1 env variable

The issue might need to be requalified, feel free to edit

EDIT: issue was edited after @klaernie feedbacks. Italic mentions the things added/updated. Strike through what was removed