Besides the bug below - documentation on 'git bugreport' does not provide any information about where to share the bug report, or explicitly say that it's not submitted (I expected the bug report to be automatically sent). --- Thank you for filling out a Git bug report! Please answer the following questions to help us understand your issue. What did you do before the bug happened? (Steps to reproduce your issue) I set the color in my Windows cmd-line window to something other than the default. I then ran 'git branch'; from that point forward, text is no longer in the colors specified by the color cmd; instead, it's the default cmdline color scheme. What did you expect to happen? (Expected behavior) see above - I expected the specified cmdline color scheme to be preserved What happened instead? (Actual behavior) Colors were rolled back to cmd.exe defaults What's different between what you expected and what actually happened? Anything else you want to add: This is a regression - this behavior worked in a build probably 3-4 years ago. I believe it was broken (but unreported) in 2.29.0 or so; it is still not fixed after this upgrade. Please review the rest of the bug report below. You can delete any lines you don't wish to share. [System Info] git version: git version 2.29.2.windows.2 cpu: x86_64 built from commit: 3464b98ce6803c98bf8fb34390cd150d66e4a0d3 sizeof-long: 4 sizeof-size_t: 8 shell-path: /bin/sh uname: Windows 10.0 19042 compiler info: gnuc: 10.2 libc info: no libc information available $SHELL (typically, interactive shell): <unset> [Enabled Hooks] post-commit
