GitHub Community
Unverified signed commit (expired) but locally verified #22179
-
|
Hello everyone, I am using a gpg key I added in 2017 to sign my commits and never had problems until now. I update the expiry date locally to keep it up-to-date. I realised today that my commits are suddenly marked as unverified with the given reason that the key is expired. Does anybody have an idea what could cause this problem?  HumanBrainProject/openMINDS_generatorContribute to HumanBrainProject/openMINDS_generator development by creating an account on GitHub. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
I figured it out. Updating an expired GPG key - GitHub DocsWhat confused me was that this never happened before. The solution was to delete the key and upload it again with the correct expiration. |
Beta Was this translation helpful? Give feedback.
I figured it out.
By looking up again how the change of expiration works in the documentation.
docs.github.comUpdating an expired GPG key - GitHub Docs
//docs.github.com/en/free-pro-team@latest/github/authenticating-to-github/updating-an-expired-gpg-key
What confused me was that this never happened before.
When I initially uploaded the key I was not in the habit of changing the expiration monthly and I guess the default expiration ended now, so that I never encountered the need to upload the new key.
The solution was to delete the key and upload it again with the correct expiration.