FAQ

Short answers to the questions that come up most. For depth, follow the links into the relevant guide.

Why not just use the Git CLI?#

You can — that's the point. GitPersona doesn't replace Git; it manages the standard mechanisms around it. Conditional includes, SSH host aliases, and credential helpers all work by hand, but they're fragile, per-machine, and easy to get subtly wrong. GitPersona manages the same mechanisms with validation on top.

Does GitPersona modify my repositories?#

It writes standard Git configuration — user.name, user.email, a signing key when set — and manages SSH and credential settings. For a repository bound to a profile, it pins that identity into the repository's local Git config. It does not touch your working tree, history, or remotes.

Can I use multiple accounts?#

Yes — that's the core use case. Give each account its own profile with its SSH key and HTTPS credential, then let assignments and rules route each repository to the right one so personal, work, and client accounts coexist on one machine.

Is my data uploaded anywhere?#

No. GitPersona is local-first: profiles and credential metadata stay on your machine, and secrets live in your OS credential vault. There is no account required for core functionality. See Credential storage.

Does it work offline?#

Yes. Switching identities, assigning repositories, managing keys, and applying rules all happen locally. Only checking for updates needs a network connection.

Which platforms are supported?#

GitPersona runs on Windows and Linux. See Installation for per-platform steps.