Allow archival of GPG keys #14008
Replies: 4 comments 3 replies
-
I agree. It's very annoying that I can't delete, get rid of or somehow 'disable' old GPG keys without making all of my thousands of verified commits... unverified. GitLab has the ability to do this - by deleting a GPG key, it won't verify new commits, but old commits won't be unverified. This is one of the very few times where GitLab's free functionality outplays GitHub pretty well. |
Beta Was this translation helpful? Give feedback.
-
I think this is a duplicate of https://github.com/orgs/community/discussions/12884. |
Beta Was this translation helpful? Give feedback.
-
I believe that now you can delete old GPG keys without the commits becoming "Unverified": https://github.blog/changelog/2022-05-31-improved-verification-of-historic-git-commit-signatures/ |
Beta Was this translation helpful? Give feedback.
-
This is still an ongoing issue with Github. Has there been any progress on this? |
Beta Was this translation helpful? Give feedback.
-
If you change computers often or perform routine wipes your GitHub account will be full of a bunch of GPG keys which become hard to manage and keep track of.
My suggestion is the ability of "archive" a GPG key. This will hide the GPG key from the default screen while still keeping all the signed commits in your history but also prevent stop any new commits from being verified when signed with that key.
I'm not 100% on the details but it would be a nice way to clean up old GPG keys that you don't use anymore but don't want to delete (to keep the commits verified)
off-topic: it would also be nice to be able to give the key's an associated name to keep track of them!
Beta Was this translation helpful? Give feedback.
All reactions