Introducing GitPersona

If you commit as more than one person — a day job, a client, a personal account, an open-source alias — you already know the cost of getting it wrong. GitPersona exists to make that cost disappear.

The problem with one Git identity

Git was built around a single global identity: one name, one email, set once in ~/.gitconfig. That works fine until you have a second one. Then it becomes a routine of manual edits — set the local config in this repo, remember which SSH key this remote wants, hope the credential Git prompts for is the right account. Miss a step and you commit as your day job on a client repository, or push to a personal project with a work email baked into the history.

None of this is exotic. It's the default experience of using Git across more than one context, and it doesn't improve by trying harder — it improves by removing the manual step.

What GitPersona is

GitPersona is a desktop app that manages Git identities as profiles. A profile bundles the things that make up "who you are" to Git and its remotes:

• A name and email — what Git writes to every commit — plus an optional GPG signing key.
• An SSH key, so the right key authenticates the right account without touching ~/.ssh/config by hand.
• An HTTPS credential, stored in your operating system's secure vault, so pushes and pulls authenticate as the right account too.

You bind a profile to a repository once. From then on, entering that repository is enough — GitPersona applies the right identity, key, and credential together, as a unit, instead of leaving you to keep three separate settings in sync by memory.

Automatic, not just organized

Binding profiles to repositories is only half of it. Rules let you match repositories by path, remote host, or owner, so new clones from a given organization pick up the right profile without manual assignment. Smart Switching runs in the background and applies the resolved profile the moment you move into a mapped repository. And for the moment it matters most, Commit Guard is a pre-commit hook that checks your identity against the repository's expected profile and warns — or blocks — on a mismatch.

Together, that's a proactive layer that keeps the right identity active, and a verification layer that catches it if something slips through anyway.

Local-first, and honest about it

GitPersona runs entirely on your machine. Secrets — tokens, private keys — never leave your OS's native secure storage: Windows Credential Manager, the macOS Keychain, or the Linux Secret Service. GitPersona's own data files hold metadata only — never a plaintext secret. There's no account to create and no server that sees your credentials, because there's no server in the loop for that at all.

Where to start

If this is the first time you're hearing about GitPersona, the documentation is the fastest way to see how profiles, rules, and switching fit together, and downloads are available for Windows, macOS, and Linux. This blog is where we'll write about the workflows it's meant to replace, and the engineering behind how it keeps your credentials safe.