Take not that full WSL interoperability needs every command to run under WSL in the current working directory for the project. What I mean is that invoking Git with "wsl git" (or bash -c "git") won't be enough for full interoperability. For instance, think about Git hooks that might run npm commands, those also need to run under WSL.
WSL/Windows paths also need to be converted from one to the other with "wsl wslpath":
I second this :)
WSL interoperability documentation:
https://docs.microsoft.com/en-us/windows/wsl/interop
Take not that full WSL interoperability needs every command to run under WSL in the current working directory for the project. What I mean is that invoking Git with "wsl git" (or bash -c "git") won't be enough for full interoperability. For instance, think about Git hooks that might run npm commands, those also need to run under WSL.
WSL/Windows paths also need to be converted from one to the other with "wsl wslpath":
https://github.com/Microsoft/WSL/issues/2715