Skip to content
GitPersonaGitPersona

Troubleshooting

Most issues come down to a mismatch between what a profile defines and what a repository actually uses. These checks resolve the common cases.

A profile doesn't appear active

  • Confirm the profile is actually applied — GitPersona shows the active profile. Applying sets your global Git identity.
  • If the repository has its own profile assignment, that per-repository identity takes precedence over the global one. Check the repository's assignment.
  • Verify the repository's local Git config hasn't been set by hand to a different user.email, which would override the global value.

SSH authentication fails

  • Check that the profile has an SSH key assigned.
  • Preview the managed SSH config and confirm the host alias, host name, and identity file are what you expect (see SSH keys).
  • Make sure the key file still exists at its recorded path and that the matching public key is registered with the Git host.
Tip: Remote host and owner rules only match when a repository has an origin remote GitPersona can parse. A repository with no remote can still match on path or name.

Credential authentication fails

  • Confirm the credential's host is one of the supported hosts and its username matches the account.
  • If you rotated a token, re-check that the profile you push as is the one the credential is assigned to.
  • Remember the secret lives in your OS credential vault — if it was removed there, re-add the token (see Credentials).

Repositories aren't detected

  • Make sure you've scanned the folders that contain your repositories.
  • Only Git repositories are tracked — a folder without a Git repository is skipped.
  • Re-run a scan after cloning new repositories, or refresh an existing one.

Still stuck?

Describe what you tried and what you expected, then reach out via the support contact on the download page.