Git commit: not respecting .gitconfig
Improvement
Git allows to configure user, email, ssh-signing-key (and other) settings depending on the folder where the repository is located.
As an example:
https://www.vincentschmalbach.com/git-includeif-the-config-superpower-you-didnt-know-about/
When committing with Yaak, I noticed that my default user/email was used, not the one configured for the repository’s folder.
Opening a terminal within the repo’s folder and running:
git commit --amend --reset-authorFixed the commit message
Would be great if Yaak could respect that setting
Linux2025.02.01
Thanks for this. Yaak is using rs-git2 and it looks easy to fetch the global config https://docs.rs/git2/latest/git2/struct.Config.html
On a related note, I plan to use the system git binary for clone/push, as there’s no way to get rs-git2 (libgit2) to use global ssh settings.
IIRC git2 is also used in gitui? I remember that there they had some blockers in allowing ssh signing commits (when the ssh private key is only provided via the ssh-agent:
https://github.com/gitui-org/gitui/pull/2047 )
Looking forward to your solution @Greg Schier :)
https://yaak.app/blog/2025.2.0-beta.2
https://yaak.app/blog/2025.2.0