-
Notifications
You must be signed in to change notification settings - Fork 458
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding a Git repo on Windows opens up the terminal window #3769
Comments
Thanks for reporting! I assume it's version 0.11.7 that you are using? |
Yes. Sorry for omitting that information initially.
I just verified that it also happens (again) when adding another repo via "Add new project" from the combobar in the upper left of an existing project. |
I started getting this with the latest nightly, it's not just adding a new repo it's basically any action for example:
Seems basically everything that causes a git operation opens the terminal for a split second. |
In my case though, actually the terminal window stays open. |
I have a feeling that this is due to Can it be that you are using a signing key or have commit signing enabled in any way? And if so, if you turn it off, does the Cmd-popup go away? Edit: With a plain installation on Windows 11 I didn't reproduce the Cmd window popup, but also know that commit signing is disabled and the added project was never touched by GB either. |
I don't have cryptographic singing of commits enabled. In some of my repos I use a commit message template to add a |
Is there a way to log which exact |
Can confirm in my case at least this seems to be the issue, disabling commit signing stopped the windows appearing. |
Thanks everyone for your help! A fix is brewing in #3800 now. |
Currently command invocations aren't specifically logged, but it's definitely something to consider. |
I was starting GitButler on Windows for the first time. When asked to add a repository, I navigated to one and selected the folder. Immediately afterwards, the Windows terminal application popped up, with no indication whatsoever why that happened.
Any idea why that happens, and how it can be avoided?
The text was updated successfully, but these errors were encountered: