From f65d32e3a1f540e16b2c5bef6429d108827ee5b3 Mon Sep 17 00:00:00 2001 From: Tim Rogers Date: Mon, 5 Sep 2022 10:04:19 +0100 Subject: [PATCH] Update "Telling Git about your X.509 key" to not assume that GPG and X.509 are the only signing options GitHub has recently introduced a third way to sign your commits alongside GPG and X.509: using an SSH key. At the moment, our copy about X.509 mentions using it "instead of GPG", which made sense when the only options were GPG or it, but now it's a bit confusing. This removes that copy. --- data/reusables/gpg/x-509-key.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/data/reusables/gpg/x-509-key.md b/data/reusables/gpg/x-509-key.md index 6848f78d42..a303466a11 100644 --- a/data/reusables/gpg/x-509-key.md +++ b/data/reusables/gpg/x-509-key.md @@ -1,7 +1,7 @@ ## Telling Git about your X.509 key -You can use [smimesign](https://github.com/github/smimesign) to sign commits and tags using S/MIME instead of GPG. +You can use [smimesign](https://github.com/github/smimesign) to sign commits and tags using S/MIME. {% data reusables.gpg.smime-git-version %}