Manage Git identities and profiles
A profile is a name and email for commits, plus an optional signing key and SSH command, that you can switch between. By default it is Passed to each git command GitTree runs, so ~/.gitconfig is never changed and a repository’s own name or email still wins; Written to ~/.gitconfig makes every git tool use it.
Works in GitTree Free: every local Git feature, once you are signed in.
On this page
Before you start
- Nothing. With no profile, your git config decides who you commit as.
Where to find it
- Preferences › Profiles.
| Action | macOS | Windows and Linux |
|---|---|---|
| Preferences | ⌘, | Ctrl+, |
Steps
Create a profile
Press New profile, give a Profile name, Name for commits (user.name) and Email for commits (user.email), and optionally a Signing key and SSH command such as
ssh -i ~/.ssh/work_key. Press Create profile.Choose how it reaches git
Under How the identity reaches git, keep Passed to each git command or choose Written to ~/.gitconfig.
Switch
Press Switch to this profile. GitTree says Switched to the profile “…”. and new commits use it.
Expected result
Your commits carry the identity of the profile you are on.
One repository, its own identity
In Repo-Specific Preferences, Name for commits and Email for commits set user.name and user.email for that repository only. A connected account can fill the email: Use an Account’s Address… lists only addresses the provider returns.
If something goes wrong
“The active profile cannot be deleted. Switch to another profile first.”
Switch to another profile, then Delete… this one. A backup of its file is kept.
Questions
Do terminals use my GitTree profile?
With Passed to each git command, only git commands GitTree runs use it; terminals and other git tools keep using your git config.