git-secrettell - adds user(s) to the list of those able to encypt/decrypt secrets.
This lets the specified user encrypt new files, but will not immediately be able to decrypt existing
files, which were encrypted without their key. Files should be re-encrypted with the new keyring by
someone who already has access in order for the new user to be able to decrypt the files.
git-secrettell works only with email addresses, and will exit with an error if you have multiple keys in
your keyring with specified email addresses, or if one of the specified emails is already associated with
a key in the git-secret repo´s keyring.
Under the hood, git-secret-tell searches in the current user´s gnupg keyring for public key(s) of passed
email(s), then imports the corresponding public key(s) into your git-secret repo´s keyring.
Versions of git-secrettell after 0.3.2 will warn about keys that are expired, revoked, or otherwise
invalid. It will also warn if multiple keys are found for a single email address.
Donotmanuallyimportsecretkeysintogit-secret. It won´t work with imported secret keys anyway.
For more details about how git-secret uses public and private keys, see the documentation for
git-secret-hide and git-secret-reveal.