Open antonengelhardt opened 1 month ago
Thank you for filing this issue.
You can try committing manually with /run git add . && git commit -m "commit message"
or similar.
Otherwise have a look at GitPython, aider uses this library behind the scenes -> https://github.com/gitpython-developers/GitPython
Thanks! I think for now i will turn the auto-commits off and experiment with aider for a bit. Just thought this might be worth flagging. Potentially something could be configured to let aider know, that i want my commits signed.
Does git commit
work for you in the terminal outside of aider? It appears to be complaining that gpg can't find the key for "xxx@icloud.com`.
Does
git commit
work for you in the terminal outside of aider? It appears to be complaining that gpg can't find the key for "xxx@icloud.com`.
Yes. I have installed pinentry in case it asks for a password. But the key is definitely there even though it says it can't find it.
The only reason I can think of why GitPython inside aider cannot see your GPG key is that aider is running in an isolated environment (container) or something like that. It that a possibility?
Now that I think about it, it may also be possible that GitPython lacks modern functionality for accessing GPG keys, which the native git binaries have no problem with.
Could be. I have never worked with GitPython tbh. But this would be a nice add-on for everyone who uses gpgsign by default
Issue
I have
git config commit.gpgSign
set totrue
.Aider fails to create commits because they cannot be signed:
Is there any way to fix this apart from turning the git flag off or turning auto-commits off?
Version and model info
v0.56.0