forked from gitea/gitea

Close #29509 Windows, unlike Linux, does not have signal-specified exit codes. Therefore, we should add a Windows-specific check for Windows. If we don't do this, the logs will always show a failed status, even though the command actually works correctly. If you check the Go source code in exec_windows.go, you will see that it always returns exit code 1.  The exit code 1 does not exclusively signify a SIGNAL KILL; it can indicate any issue that occurs when a program fails.