docs: add workaround for verbose Windows output to README FAQ

.changeset/giant-starfishes-vanish.md

@@ -0,0 +1,2 @@
+---
+---

README.md

@@ -644,7 +644,7 @@ module.exports = {
 
 ## Frequently Asked Questions
 
-### The output of commit hook looks weird (no colors, duplicate lines, …)
+### The output of commit hook looks weird (no colors, duplicate lines, verbose output on Windows, …)
 
 <details>
   <summary>Click to expand</summary>
@@ -660,6 +660,21 @@ https://raw.githubusercontent.com/git/git/master/Documentation/RelNotes/2.37.0.t
 >   hook, which was noticed post release. This is getting corrected.
 >   (merge [a082345372](https://github.com/git/git/commit/a082345372) ab/hooks-regression-fix later to maint).
 
+If updating Git doesn't help, you can try to manually redirect the output in your Git hook; for example:
+
+```shell
+# .husky/pre-commit
+
+#!/usr/bin/env sh
+. "$(dirname -- "$0")/_/husky.sh"
+
+if sh -c ": >/dev/tty" >/dev/null 2>/dev/null; then exec >/dev/tty 2>&1; fi
+
+npx lint-staged
+```
+
+Source: https://github.com/typicode/husky/issues/968#issuecomment-1176848345
+
 </details>
 
 ### Can I use `lint-staged` via node?