Re: Pushing to the repos

On 03-08-2022 20:02, Maxime Devos wrote:
>
> On 03-08-2022 19:47, Willow Liquorice wrote:
>> Hello,
>>
>> Given that I'm getting repository access soon, I'm getting my changes 
>> ready to be pushed.
>>
>> I need to sign my commits, is that with the SSH key pair?
>
> Signing commits is done with GnuPG, telling git.gnunet.org that you 
> are allowed to do stuff there is done with SSH; you will need to 
> create both and share the public parts -- the public part of the SSH 
> key is only needed by those who manage that machine, the public part 
> of the GnuPG is required to be public (such that people can verify the 
> commits).
>
> I recommend adding
>
> [commit]
>     gpgsign = true
>
> to .gitconfig to automatically sign commits.
>
>> Is the guide in the developer's manual in line with current practice? 
>> I've never used a VCS collaboratively before, and I'm a bit worried 
>> about screwing up my first major contribution.

I do not know if there's a guide there, maybe there is, but I haven't 
looked myself.

Greetings,
Maxime.

-----BEGIN PGP PUBLIC KEY BLOCK-----

xjMEX4ch6BYJKwYBBAHaRw8BAQdANPb/d6MrGnGi5HyvODCkBUJPRjiFQcRU5V+m
xvMaAa/NL01heGltZSBEZXZvcyA8bWF4aW1lLmRldm9zQHN0dWRlbnQua3VsZXV2
ZW4uYmU+wpAEExYIADgWIQTB8z7iDFKP233XAR9J4+4iGRcl7gUCX4ch6AIbAwUL
CQgHAwUVCgkICwUWAgMBAAIeAQIXgAAKCRBJ4+4iGRcl7japAQC3opZ2KGWzWmRc
/gIWSu0AAcfMwyinFEEPa/QhUt2CogD/e2RdF4CYAgaRHJJmZ9WU7piKbLZ7llB4
LzgezVDHggzNJU1heGltZSBEZXZvcyA8bWF4aW1lZGV2b3NAdGVsZW5ldC5iZT7C
kAQTFggAOBYhBMHzPuIMUo/bfdcBH0nj7iIZFyXuBQJf56ycAhsDBQsJCAcDBRUK
CQgLBRYCAwEAAh4BAheAAAoJEEnj7iIZFyXujpQBAKV1SwDDl4f24rXciDlB9L8W
ycZt30CgbewMSRQk4mvbAP9dFMbVVixYBd6C8cfhR+NsOBGiOJnQABlUmgNuqGFJ
Dc44BF+HIegSCisGAQQBl1UBBQEBB0BOlzIWiJzgobMF6/cqwLaLk7jIcFSZ++c0
k9cCNT6YXwMBCAfCeAQYFggAIBYhBMHzPuIMUo/bfdcBH0nj7iIZFyXuBQJfhyHo
AhsMAAoJEEnj7iIZFyXuMr0BAJc8cl5PGvVmVuSQVKjleNl4DK1/XAaPAYPe34AE
fZJPAP9IqLCQhH/FeJanHqBP8gNdGNI2qn8RnnLVfRJgUjZ1BA==
=OVqp
-----END PGP PUBLIC KEY BLOCK-----