GPG signing
A profile can carry a signing key reference, so the correct key is used for signed commits whenever that profile is active.
Overview
The signing key is part of a profile's identity, alongside name and email. It is optional — profiles that don't sign simply leave it empty.
Configuring a signing key
Set the signing key when you create or edit a profile. When the profile is applied, GitPersona includes the signing key in the Git configuration it writes, so your commits are signed with the key that belongs to the active identity. Leaving the field blank means no signing key is set for that profile.
What GitPersona does and does not do
- Does — reference a signing key per profile and apply it as part of switching, so the right key is configured for the right identity.
- Does not — generate, import, or otherwise manage cryptographic signing keys. You create and manage the key with your own tooling; GitPersona only points Git at it.
Note: Because GitPersona references an existing key rather than managing key material, make sure the key is already present and usable by Git on the machine before enabling signing for a profile.
For how commit author identity is applied, see Switching profiles.