-
Notifications
You must be signed in to change notification settings - Fork 27
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
Not possible to submit signed Git commits #69
Comments
Hi, thanks for your report! You're right, we currently don't have any support for signing commits. LibGit2sharp does support it, but only at a pretty low level. I'm going to look into this to see if it is possible to add support for this. |
Hello geluk, |
Implemented as of v1.11. |
Hello @geluk
After making a change in pass-winmenu HEAD gets detached and points to the new commit:
Then I can't automtically push to remote anymore, I first have to create a new branch with the new commit and merge this to master.
Is this intentionally? Can you elaborate the workflow behind this? I would have expected that the signed commit gets committed the same way as an unsigned commit. |
It is intentional in the sense that creating the commit needs to be done manually, as LibGit2Sharp does not have support for creating signed commits in the same way as regular commits. However, forgetting to resolve the I've created a new commit that fixes this this issue for me, could you check if it has been fixed for you as well? You can download a build of |
Wonderful, this fixes the issue! Signed commits work now for me. |
My password store is synced with a Git repository that only accepts signed commits. Hence my Git config includes:
Committing changes via git.exe works without problems. When I issue a git commit, the GnuPG Pinentry dialog automatically pops up and asks for the passphrase of my GPG key.
Now for the problem with pass-winmenu, which otherwise works nicely: In the config I set
sync-mode: native-git
git-path: 'C:\Program Files\Git\bin\git.exe'
When I add a new password, pass-winmenu does create a new commit, but it is not signed, which causes Push to remote to fail with error code 1. I don't see a Pinentry dialog either. The Pinentry dialog however IS shown when decrypting a password.
The text was updated successfully, but these errors were encountered: