Skip to content
OpenChamber
↑↓Navigate ↵Open escClose

Git Identities

A git identity is the name and email your commits carry, and the way a repository signs in to its remote. If you work across personal and work repos, you can save identities and apply the right one per repository. Manage them at Settings → Git.

Add an identity

  1. Open Settings → Git and choose New.
  2. Enter the User name and Email address to commit with.
  3. Pick an Auth method, how it pushes and pulls:
    • This machine: whatever Git on this machine already uses, such as SSH keys, a credential manager or the gh CLI
    • Account: the Source control account you pick, any account connected on a host card in Integrations, such as GitHub, GitLab, Gitea, Forgejo or Gerrit; pushes go over HTTPS with that account’s token
    • SSH: a key OpenChamber keeps for this identity
    • Anonymous: reads public repositories over HTTPS without signing in, and can’t push
  4. Optionally give it a color and icon so it’s easy to spot.

Your system’s global identity is shown too, as read-only.

On Gerrit, an account identity signs in to Git with your Gerrit username and the HTTP password you connected. A GitHub Enterprise account serves issues and pull requests, but cloning and pushing there go through This machine or SSH.

Apply an identity to a repo

Choose the identity button at the top of the Git panel and pick one. The add and clone screens offer the same choice. An identity that can’t reach the repository stays in the list, turned off, with the reason: an account on another host, an account or Anonymous on an SSH remote, or an SSH key on an HTTPS remote.

Applying an identity writes it to that repository’s local git config, so it affects only that repo and your global setting stays as it is. Git in the terminal and the agent’s shell use it too. System identity removes what OpenChamber wrote, so your own Git configuration answers again.

SSH key passphrases

For an encrypted SSH key, enter its optional passphrase before Find keys in ~/.ssh, then confirm the fingerprint and add the key. OpenChamber keeps the key encrypted and saves the passphrase in OpenCode’s credential store. Saved passphrases work only for Git actions in the app. Terminal and agent-run Git commands do not retrieve them, so an encrypted managed key cannot authenticate through that path.

  • Git Workflows: commit using the identity you set
  • Git hosts: connect an account on GitHub, GitLab, Gitea, Forgejo or Gerrit