In this chapterUnderstand how accounts, identity rules and the Git workspace fit together.
Many developers have more than one Git identity: a work account, a personal one, perhaps accounts for clients. Git itself doesn’t know which one you mean, so it’s easy to:
- push with the wrong SSH key and get “Permission denied (publickey)”,
- commit with your personal email on a work project (or the reverse),
- end up with a complicated
~/.ssh/configfull of host aliases.
GitTrail solves this once:
- You add each account (name, email, SSH key, optional token).
- You tell GitTrail which account belongs where: one repo, a whole folder, or every repo from an organisation.
- From then on, every commit and push uses the right account automatically, in GitTrail and in any other Git tool.
On top of that, GitTrail is a full visual Git client: a colourful commit graph, drag-and-drop merging, a conflict editor, pull requests, CI, and undo for everything.
GitTrail has three faces that share the same engine:
| Face | How to open it | Good for |
|---|---|---|
| Desktop app | gittrail ui, or the app icon |
Everyday work, visual Git |
| Interactive terminal | gittrail with no arguments |
Quick account picking in a terminal |
| Commands | gittrail use work, gittrail doctor… |
Scripts and power users |
Need another approach?Find a fix →