y, and more recently (since
>>> Git 2.34) also started supporting signing with an SSH key. The latter
>>> is IMHO much easier to set up, because anybody who can push to the GCC
>>> repo already has an SSH key configured.
>>>
>>> To start signing your
SSH key. The latter
>> is IMHO much easier to set up, because anybody who can push to the GCC
>> repo already has an SSH key configured.
>>
>> To start signing your git commits, just enable commit.gpgsign (which
>> also enables signing with SSH, despite the name) an
The latter
> > is IMHO much easier to set up, because anybody who can push to the GCC
> > repo already has an SSH key configured.
> >
> > To start signing your git commits, just enable commit.gpgsign (which
> > also enables signing with SSH, despite the name) and tell Git w
t; repo already has an SSH key configured.
>
> To start signing your git commits, just enable commit.gpgsign (which
> also enables signing with SSH, despite the name) and tell Git where to
> find your public key. To use SSH keys instead of GPG, set
> gpg.format=ssh. I suggest the ssh k
Git supports signing commits with a GPG key, and more recently (since
Git 2.34) also started supporting signing with an SSH key. The latter
is IMHO much easier to set up, because anybody who can push to the GCC
repo already has an SSH key configured.
To start signing your git commits, just enable
