Re: Pushing to the repos
Martin Schanzenbach <[email protected]>
| Newsgroups | gmane.network.gnunet.devel |
|---|---|
| Message-ID | <1659550170-sup-7572@werkbank> |
Excerpts from Willow Liquorice's message of 2022-08-03 18:47:35 +0100: > Hello, > > Given that I'm getting repository access soon, I'm getting my changes > ready to be pushed. > You should already have permissions. > I need to sign my commits, is that with the SSH key pair? 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. > You need to sign your commits with GPG. There are guides on how to configure that for git on the Internet, e.g. https://git-scm.com/book/en/v2/Git-Tools-Signing-Your-Work Dont worry about it, the nice thing about git is that we can always revert to an old state. If you want, you can also learn to use branches. Dev branches in gnunet (as described in the handbook) also allow you full control (e.g. deletion of the branch) while master and others are protected. Br > Regards, > Willow
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEPREGPBD5jRS9JNFHCwmY74b1m2oFAmLqumoACgkQCwmY74b1 m2rMow//SSn4Ib1hhY7IL0DJDL1oefSwhe2pn4Rzjg3QrXYsf8G/e2OppDe//CNb MzzUNROaOKXN3TcdQrwk5b9epPjdNUm9szNQVzhEs/U4kNF71qoefGjR+ak46f3G eRROEiFbdgRYfo6eqLaowLg6PWYzhVY/XYdrtSqHEkpp+7zk8PvVMJkz/ISUunzq FJ6izxz7qhp2M9gAtqKPPE4UqxZ+a79D+GbU7vKRAQp4/N0yF+1ELuM17qKUBjgK aRiG1aIVi9FqNf7WH+p6QUp+VTzzKdWQXDOMoSV+Z0BsjM4WGxtHHhi7JhEc0q8z XskkvO3HEFjL1LNQ57Ylm9pzVSQknl4BNXJyJvGpU/Q0pmoZEY8tINrzR20yOwdy pwWXi9NxQKL4zLGiu0vFKobyOIJu7K1KjngqAWEaUGW+TxaZgvhx2Rhcdt1EaUnQ x+odhVIvpoFCbGx5jCWXJRyeqDPDRL/voroOzXBfwq7qeF+5IQLOpkbvEpOJeBox elINJvM/8uaiLV4q6KlmnNlhHajrMDcfPLtA6BLdEhvwWIOhzIRj7S/A6GqGtLir Qp8jLIiroWXkdg5awoLlugdxsUxiYVcNqIYnFo/NCgRjS3/bNWkFVFBuPRmd0VLA AjaAvNxg8Iib7ywj3+J1mNV2FmkOQ8FBwsXOollVB2tazi/vTA4= =F1Xl -----END PGP SIGNATURE-----