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
The logs can be rather monotonous when looking for errors.
The cpp-linter python package already has support for using the rich package to add color and style to log outputs. This action only needs to ensure rich is installed if users want colored (and stylized) output in the CI logs.
Acceptable values that mean "color enabled" include true, on, and 1. By default, color output should be disabled because the ASCII color codes are included in the raw logs that can be downloaded to a text file.
Describe alternatives you have considered
No response
Additional context
The cpp-linter-rs project already includes support for this env variable (see cpp-linter/cpp-linter-rs#52), and it does not require additional dependencies installed. Migrating this new feature to use the rust project should be seamless.
The text was updated successfully, but these errors were encountered:
Is your idea related to an existing feature?
verbosity
Describe the behavior you would like
The logs can be rather monotonous when looking for errors.
The cpp-linter python package already has support for using the
rich
package to add color and style to log outputs. This action only needs to ensurerich
is installed if users want colored (and stylized) output in the CI logs.Proposal
Acceptable values that mean "color enabled" include
true
,on
, and1
. By default, color output should be disabled because the ASCII color codes are included in the raw logs that can be downloaded to a text file.Describe alternatives you have considered
No response
Additional context
The cpp-linter-rs project already includes support for this env variable (see cpp-linter/cpp-linter-rs#52), and it does not require additional dependencies installed. Migrating this new feature to use the rust project should be seamless.
The text was updated successfully, but these errors were encountered: