Good article! Though I don't know if I'm understanding the subject incorrectly but I think the git commit flag needed to sign (in the sense of using you gpg keys to sign the commit) is -S and not -s. I'm assuming that the "git.enableCommitSigning": true option is adding -S correctly. My git man pages reads:
-s, --signoff
Add Signed-off-by line by the committer at the end of the commit log message. The meaning of a signoff
depends on the project, but it typically certifies that committer has the rights to submit this work under
the same license and agrees to a Developer Certificate of Origin (see http://developercertificate.org/ for
more information).
-S[<keyid>], --gpg-sign[=<keyid>]
GPG-sign commits. The keyid argument is optional and defaults to the committer identity; if specified, it
must be stuck to the option without a space.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Good article! Though I don't know if I'm understanding the subject incorrectly but I think the
git commitflag needed to sign (in the sense of using you gpg keys to sign the commit) is-Sand not-s. I'm assuming that the"git.enableCommitSigning": trueoption is adding-Scorrectly. My git man pages reads: