GPG support? (like SSH)

IMO, GPG is a fairly complex standard that sees use in many many ways. Adding support for all of these myriad ways into 1Password maybe reinventing the wheel because GPG already has a large number of tools available. And these tools are quite modern in their implementation (but often not in their UI/UX). 

At the same time, I do want to be able to store my GPG keys in 1Password. After all, what I am paying for is having to remember just "one password". 

Yes, PLEASE add this feature! +++++
Years ago, I set up PGP for mail, git signing, and SSH as well.
1Password SSH features are great but they don't work with this PGP "ecosystem".
I have had to convert my keys and change my workflow which was very complicated.

Just to throw my opinion into the mix: SSH keys cannot be substituted for PGP keys in all cases. A PGP key is closer to a digital certificate than it is to an SSH key; whereas an SSH key is really just a raw public key with a tiny amount of metadata attached, a PGP key can and generally does contain a wealth of additional metadata, and is also used for a much wider variety of purposes, like certifying other public keys or containing attached subkeys.

In concrete terms, an SSH key cannot be substituted for a PGP key for many use cases, like E2E encrypted email, YubiKey, cryptocurrency wallets etc. If 1Password were to support a GnuPG authentication agent, it would make storing private keys in a centralized location easier and more secure, and the process of performing common PGP-related tasks more transparent.

While GnuPG is pretty widely supported nowadays, and there is a wide variety of FOSS out there for managing keys, having my PGP keys stored in 1Password would make life a little easier. It's a small quality-of-life improvement, but not really a significant ask from me personally. I use 1Password because it has the best user experience and broadest compatibility of all of the password managers I've tried, and I intend to keep using it regardless of whether or not PGP keys are supported.

+1
GnuPG, multiple use cases, sign/encrypt archive, sensitive information, emails, etc.

Big +1

SSH commit signing is fine until you need to rotate keys. Revoking a GPG key will continue to show commits in GitHub (unsure about GitLab) as "verified (expired)". The only way I've found to do the same with SSH keys is to remove the old key completely, but then commits show as "unverified" which defeats the point of supply chain integrity since it's not possible to distinguish a commit that was signed with an old key, or a commit that was not signed, or signed with another key that's not allowed.

The alternative is to not rotate signing keys, but then you compromise supply chain integrity further by not ensuring keys are rotated in a timely fashion.

+1

Please add GPG support! It would be amazing.

+1. I'd like to be able to store GPG subkeys in 1Password and instead of entering a PIN like I currently do with subkeys stored on a Yubikey I'd just use fingerprint. Subkeys would sync with other machines in the same way SSH keys (and everything else) do. I've already switched to using SSH with 1Password for signing Git commits, mostly for the convenience. If there was GPG support though I'd probably use GPG for Git signing again. However, I also use GPG for encryption of files, it's especially useful for encrypting and authing to things like email services etc when using Emacs which is my editor of choice.

I can't wait to see this feature. GPG keys are not only for Git as you know and hard to store it securely. This will be very useful for business users also.

+1