>Not sure what you mean by 'script file'. Git.exe is a console application so you can automate it with batch files or powershell. Certainly no different from using Bash, but without the overhead of the extra shell. That just seems like an odd choice on a Windows system.

...a series of commands

But, this is all resolved now. The .NET Process class invoke a call for each Git command I need to execute. And, that works ok.

With Git.exe, the Process file does not lock on WaitForExit(). With the bash interpreter, it never ends.