Flip --incompatible_windows_bashless_run_command
Fixes
RELNOTES[INC]: Windows: --incompatible_windows_bashless_run_command is now true by default, meaning "bazel run //foo:bin" will run the binary as a subprocess of the Bazel client. (When the flag is false, the binary is executed as a subprocess of Bash.)
@@ -135,7 +135,7 @@ public class RunCommand implements BlazeCommand {
OptionMetadataTag.INCOMPATIBLE_CHANGE,
OptionMetadataTag.TRIGGERED_BY_ALL_INCOMPATIBLE_CHANGES,
},
- defaultValue = "false",
+ defaultValue = "true",
help =
"On Windows: if true, the \"run\" command runs the binary directly instead of running "
+ "through Bash; when false, then the binary is ran through Bash. On other "
