This is a follow-up to #3110, and I am not sure it is valid, but I wanted to at least bring it up.

Running WSL on Windows means one can easily use a Windows file system as working directory. However, such file system do not support the executable flag, so to make anything executable, everything is considered executable (see also microsoft/WSL#936). That triggers EXE002.

So I wonder if #3111 could be extended to ignore not only Window operation system, but also Windows file systems on Linux. One way of detecting such file systems would be by creating a new file and checking if it is executable:

bers@hostname:~$ touch foo
bers@hostname:~$ ll foo
-rw-r--r-- 1 bers bers 0 Jun 29 20:06 foo
bers@hostname:~$ cd /mnt/c/Code/project
bers@hostname:/mnt/c/Code/project$ touch foo
bers@hostname:/mnt/c/Code/project$ ll foo
-rwxrwxrwx 1 bers bers 0 Jun 29 20:06 foo*