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.
Repository owner locked and limited conversation to collaborators on Nov 27, 2024
Activity
love-linger commentedon Nov 14, 2024
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.aikawayataro commentedon Nov 14, 2024
I think it is safe to send
SIGTERMto gracefully stop git as it installs a handler for this. The problem is there's no dotnet API for such thing dotnet/runtime#109432albertodlc commentedon Nov 14, 2024
GitExtension allow this behavior. And it is based on dotnet (I think) so maybe we can replicate their approach.
aikawayataro commentedon Nov 14, 2024
Their approach is Windows-only
It is possible to use p/invoke and call whatever we need for the corresponding OS but that's cumbersome
dougcunha commentedon Nov 16, 2024
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.