

So, you cannot run a dev server in WSL, as code changes made a Windows editor will not be reflected in the dev server. WSL does not trigger file handlers when the file is changed in Windows tools. ps: $env:Path = "C:\Program Files\Git\bin $env:Path" # Make sure we get the bash that comes with git, not WSL bash If your program depends on Git bash (and not WSL/WSL2 bash), make sure to put said Git for Windows first in your PATH, as Jon Skeet described in "USING “GIT BASH” FROM APPVEYOR", in an AppVeyor CI environment. Git Bash is an application for Microsoft Windows environments that provides an emulation layer for a Git command-line experience. Note: WSL will soon be replaced by WSL2, which uses an entirely new architecture that uses a real Linux kernel. The Git for Windows is based on a POSIX compatibility layer, which has limitations: POSIX support is deprecated since Windows 8. bash is a shell (bash is really an acronym for Bourne Again SHell), and its a very popular shell on unix-like systems, uncluding Linux but also on other systems like OS-X. That is vastly different from WSL, which emulates an actual Linux distribution.ĭoes it contain some constraints that WSL doesn't have? See more in "How are msys, msys2, and msysgit related to each other?". Git Bash is a package that installs Bash, some common bash utilities, and Git on a Windows operating system.


Bash is a popular default shell on Linux and macOS. A shell is a terminal application used to interface with an operating system through written commands. Git for Windows is using the mingw-w64 project (as illustrated here) and msys2. Bash is an acronym for Bourne Again Shell.
