Describe the bug
This may be a bug or a feature request. I have used many tools similar to Git cz, and they all read commit.gpgSign=true and sign the commit accordingly. However, our tool does not; it even bypasses Git's commit signing check hook. In this sense, it doesn't work as expected.
To Reproduce
I am signing with an SSH key. According to this article, the signing works correctly when I run git commit or git commit -S manually.
Expected behavior
When I check with git show/log --show-signature, if the commit is properly signed, the output should display something like: Good "git" signature for my@email.com with RSA key SHA256:hash or something?
Screenshots
Environment
OS:
Version: Installed with cargo install, so the version should be v0.1.1.
Of course, if you are a little busy, I might be able to take a look and submit a related PR this weekend.
And I noticed that the git-cz command does not have --version
Describe the bug This may be a bug or a feature request. I have used many tools similar to Git cz, and they all read
commit.gpgSign=true
and sign the commit accordingly. However, our tool does not; it even bypasses Git's commit signing check hook. In this sense, it doesn't work as expected.To Reproduce I am signing with an SSH key. According to this article, the signing works correctly when I run
git commit
orgit commit -S
manually.Expected behavior When I check with
git show/log --show-signature
, if the commit is properly signed, the output should display something like:Good "git" signature for my@email.com with RSA key SHA256:hash or something?
Screenshots
Environment
OS:
Version: Installed with
cargo install
, so the version should be v0.1.1.Additional context
None