You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's not safe to cancel a running git command directly. You can use git config --global http.timeout <SECONDS> to reduce the waiting time of network connection.
I think it is safe to send SIGTERM to gracefully stop git as it installs a handler for this. The problem is there's no dotnet API for such thing dotnet/runtime#109432
I also intended to propose this feature. I've experienced significant delays cloning GitHub repositories in SourgeGit, with no option to cancel except by forcefully terminating the SourgeGit processes. Although the cloning issue can be problematic in itself, a dedicated cancel button would be a valuable addition.
Allow users to cancel running commands to avoid waiting until the error message is displayed.
Example
I tried to push a commit and I didn't have connectivity with the remote, so I had to wait until Sourcegit return an error
The text was updated successfully, but these errors were encountered: