You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following command starts the gpg-agent on Windows: gpg-connect-agent reloadagent /bye
Alternatively, committing via e.g. SourceTree at least once will somehow start the GPG agent, and then I can continue using GitHub Desktop for more commits on the same day.
Would much prefer GitHub Desktop to handle the daemon-start for me.
The text was updated successfully, but these errors were encountered:
@Vectorial1024 thanks for the issue, and apologies for the delay here. We've seen this reported in #14274, but haven't dug into it as of yet. I'm going to close this out and reference this there.
The problem
I have enabled GPG key signing on commit.
Sometimes, especially when committing for the first time of the day, I got this popup message saying GH Desktop cannot sign my commits:
Would this be a potential problem of GitHub Desktop?
Release version
3.3.14
Operating system
Windows 11
Steps to reproduce the behavior
No response
Log files
No response
Screenshots
Additional context
Manually starting the keybox daemon will fix this; e.g. ref https://superuser.com/questions/1153101/why-does-git-complain-that-no-gpg-agent-is-running
Alternatively, committing via e.g. SourceTree at least once will somehow start the GPG agent, and then I can continue using GitHub Desktop for more commits on the same day.
Would much prefer GitHub Desktop to handle the daemon-start for me.
The text was updated successfully, but these errors were encountered: