Nothing to try yetTier: how much it should matter to you
1Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Git SecurityArea: what it touches
In DevelopmentKind: in v2.1.274,
In DevelopmentSection of the release
Unclear Whether these new keys and forced values are actually applied anywhere, or just defined, is not shown by the evidence.
What
A new regular expression matching git signing-related configuration keys, such as tag.gpgsign, user.signingkey, gpg.format, and gpg.program, was added, along with a paired list of key/forced-value combinations like tag.gpgSign set to false and gpg.ssh.defaultKeyCommand set to empty.
Why
This extends the earlier work that let Claude Code trust and automatically configure git signing settings for commits, now recognizing more signing-related keys such as tag signing settings, though the finding doesn't show these new entries actually being applied yet.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhether these new keys and forced values are actually applied anywhere, or just defined, is not shown by the evidence.
