feat(git-node): add support for the --gpg-sign git flag

[aduh95]

I've also extended the max line length from 80 to 100 as it was making less readable to keep it at 80 IMO.

[codecov]

Codecov Report

Patch and project coverage have no change.

Comparison is base (b9c443b) 83.45% compared to head (191513b) 83.45%.

Additional details and impacted files

@@ Coverage Diff @@## main #684 +/- ##
=======================================
Coverage 83.45% 83.45% =======================================
Files 37 37 Lines 4158 4158 =======================================
Hits 3470 3470 Misses 688 688 

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[aduh95]

ping @nodejs/node-core-utils

[targos]

I personally set this in my git config. What's the advantage of this flag compared to it ?

[aduh95]

The flag let's you select a specific keyid to sign the commit with.

[targos]

In the git config you can set ˋuser.signingkey` with the key id

[aduh95]

If you have set a specific key id in your git config, the flag lets you specify a different one.

[targos]

I still don't understand the use case. Don't you always use the same key for the node repo?

[aduh95]

No, I usually don't sign my commits for the node repo (why would I, the CQ would sign them for me), but in the rare cases when I need to push manually to main, I have to do the git commit --amend --no-edit -S dance, and it seems easy to add the flag to ncu instead.