TTY_INTERACTIVE env var #3777
TTY_INTERACTIVE env var #3777
Conversation
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## master #3777 +/- ##
==========================================
- Coverage 98.24% 97.85% -0.40%
==========================================
Files 74 74
Lines 8105 8142 +37
==========================================
+ Hits 7963 7967 +4
- Misses 142 175 +33
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
I assumed that this option had something to do with interactive terminals, where you can not read from stdin. But, If I understand you correct, you are still able to read user input, even when TTY_INTERACTIVE=0 is enabled. Maybe call it TTY_ANIMATION=0 |
|
It echos an existing attribute in Rich. In that context interactive means somebody (i.e. a human) is interacting with the terminal, as apposed to running on CI. You are still able to read input, but reading from stdin doesn't always requires a human operator. It does disable animation, but the flag in Rich has broader meaning. It could also be |
Adds a
TTY_INTERACTIVEto disable things like progress bar / status spinners in CIThis adds to the new
TTY_COMPATIBLEwhich enables styles even when the file is not technically a tty, as is the case in Github Actions.TTY_INTERACTIVE=0will remove superfluous animations and progress bars in the CI output.