-
Notifications
You must be signed in to change notification settings - Fork 575
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
Broken git signing #7467
Comments
Thanks a lot for reporting! Could you try to run GitButler from a terminal (where Git CLI signing works) using If this works, we know that the environment is causing the issue. Here is where one could assure a shell is always used to invoke the GPG program, something that typically picks up more of the environment (but not necessarily all) that the user sees in a terminal. gitbutler/crates/but-core/src/cmd.rs Lines 4 to 17 in 2e0d0d7
If you confirm, I think we should just always invoke it in a shell to increase the chances of successful operation. |
This way there are higher chances of picking up the required PATH configuration, making signing operations more likely to work.
This way there are higher chances of picking up the required PATH configuration, making signing operations more likely to work.
) The `SHELL` environment variable is set on MacOS to represent the login shell. It is probably more likely to yield an environment that can run the signing program. Note that doing so usually is dangerous as well if scripts were to be used, but that's not the case here - we know a program is provided.
Run GPG in shell on Unix as well (#7467)
Version
0.14.8
Operating System
macOS
Distribution Method
dmg (Mac OS - Apple Silicon)
Describe the issue
I'm using macos gitbutler with nix-darwin based gpg. Whenever I try to enable git signing, I always get this error
It used to work on a nightly version of gitbutler (I commented about it in #5022), but it's not working anymore. I don't know the exact version when it stopped working, but I can check it if you need it.
Also, git signing works normally on normal cli git.
How to reproduce (Optional)
No response
Expected behavior (Optional)
No response
Relevant log output (Optional)
The text was updated successfully, but these errors were encountered: