-
-
Notifications
You must be signed in to change notification settings - Fork 423
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Verbose output on windows #1277
Comments
yeah same for me, it was prettier in previous versions |
same issues |
Lint-staged relies on Listr2 to determine how the log should look like. You can play around with this file to see if you manage to make it look nicer, unfortunately I don't have a Windows machine myself to debug: https://github.com/lint-staged/lint-staged/blob/master/lib/getRenderer.js EDIT: For example, forcing |
@iiroj Thank you. I will have a try later. what i want to attach, is that: |
This is probably related to the issue described in our FAQ: https://github.com/lint-staged/lint-staged?tab=readme-ov-file#the-output-of-commit-hook-looks-weird-no-colors-duplicate-lines- |
No, git version is 2.43.
So it should report to git team? |
Does this help? If so, I can add it directly to the README: typicode/husky#968 (comment) EDIT: That is, adding this to your husky script before # If tty is available, apply fix from https://github.com/typicode/husky/issues/968#issuecomment-1176848345
if sh -c ": >/dev/tty" >/dev/null 2>/dev/null; then exec >/dev/tty 2>&1; fi |
Yes, after add this line to huksy, it work as expect. Thanks you. |
Description
I just added lint-staged to my project and it works fine. However, the output seems to be quite verbose and not nicely formatted as I saw it in examples.
Steps to reproduce
Configure minimal example and make a commit to trigger the hook.
Output:
Wanted:
Something in the style of this:
Environment
lint-staged
: 13.2.0The text was updated successfully, but these errors were encountered: