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
{{ message }}
This repository has been archived by the owner on Oct 1, 2024. It is now read-only.
GitHub Actions supports colour terminal output, but Rich disables it when it detects it's not writing to a terminal.
We should check environment variables, and if we're on a CI platform that we know supports colours, force Rich to write them as described here: Textualize/rich#52 (comment)
Hi @darrenburns, I can work on this issue if no one else has.
I'm comfortable with Python and have used ward before, but haven't contributed much to open source projects, so I thought I would try to help with this.
GitHub Actions supports colour terminal output, but Rich disables it when it detects it's not writing to a terminal.
We should check environment variables, and if we're on a CI platform that we know supports colours, force Rich to write them as described here: Textualize/rich#52 (comment)
We can detect that we're running on GitHub Actions by looking at the env var described in here: https://docs.github.com/en/actions/reference/environment-variables#default-environment-variables
We should also allow the user to force colour output by passing a command line flag.
Example of output in our CI pipeline just now:
The text was updated successfully, but these errors were encountered: