Skip to content
GitPersonaGitPersona

Profiles

A profile is the central object in GitPersona: a named Git identity you can activate globally or bind to repositories. Everything else — SSH keys, credentials, rules — attaches to a profile.

Anatomy of a profile

A profile holds:

  • A label — the display name you pick, e.g. Work.
  • An identity — the name and email written to Git config, plus an optional signing_key.
  • An optional color for quick visual recognition.

The identity is the part Git actually consumes. When the profile is active, its name and email are what appear on your commits.

Managing profiles

From the Profiles view you can:

  • Create a profile with a label, name, email, and optional signing key and color.
  • Edit any field on an existing profile.
  • Delete a profile you no longer need.
  • Apply a profile to make it the active identity.
Note: There is no cap on the number of profiles. Create one per account — personal, each employer, each client — and let assignments and rules route repositories to the right one.

Keys and credentials

A profile becomes a complete identity once you attach the credentials it authenticates with:

  • Assign an SSH key so SSH remotes connect as the right account.
  • Assign an HTTPS credential so HTTPS pushes and pulls authenticate correctly.

These attachments follow the profile: activating it makes its key and credential the active ones.

The active profile

Exactly one profile is globally active at a time, and GitPersona always surfaces which one. Repositories can override the global choice through a per-repository assignment — see Switching profiles and Rules.