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
In addition to logging to stdout/stderr when using the triage CLI, we should make it easier to ensure logs get captured to a file as well (although users could do this by redirecting the output, logging to a file would be good default behavior generally and providing some arguments to control it might be easier for users unfamiliar with bash).
A few features that seem like they would be useful:
Log to a file in the project path by default, identified by the current timestamp (in addition to logging to the terminal)
Allow specifying a log file name/path via a CLI argument
Arguments to suppress logging to the terminal and/or file might be nice to have as well (e.g., --quiet)
The text was updated successfully, but these errors were encountered:
In addition to logging to stdout/stderr when using the triage CLI, we should make it easier to ensure logs get captured to a file as well (although users could do this by redirecting the output, logging to a file would be good default behavior generally and providing some arguments to control it might be easier for users unfamiliar with bash).
A few features that seem like they would be useful:
--quiet
)The text was updated successfully, but these errors were encountered: