Accounts

In this chapterCreate an account and check its connection status.

An account is one identity. The Accounts page lists them on the left and shows the selected one on the right, with live status checks.

Add an account

• Quick add from GitHub: sign in once in your browser. GitTrail fills in your name, verified email and username, creates a new SSH key and adds it to that GitHub account. Repeat for each GitHub account. (Needs the GitHub CLI, gh.)
• Quick add from GitLab or Bitbucket: paste a token; name, email and SSH key are set up for you.
• Add manually: name, email, provider and host, username, and an SSH key (pick an existing one or create a new one).
• Import: GitTrail finds accounts in your Git config, folder rules and ~/.ssh/config. Accounts › Import or gittrail import.
• From the terminal: gittrail add starts a guided wizard.

Supported hosts: GitHub, GitHub Enterprise, GitLab (and self-managed), Bitbucket, Azure DevOps, Gitea/Forgejo, Gitee, SourceHut, AWS CodeCommit, and any other Git server.

ℹ️ This version works with GitHub. GitLab, Bitbucket, Azure DevOps and the other hosts listed above are coming soon; they aren’t available to use yet.

Status at a glance

Each account shows one verdict from live checks: Connected, Ready (HTTPS), Key not on host, Login fails, Wrong key, No token… Click it to see the details and a fix button for each problem. Refresh status checks again.

SSH keys

• Make a key: Set up SSH creates an ed25519 key and shows the public part.
• Add it to the host: GitTrail uploads it with gh or glab, and refuses if that tool is signed in as someone else.
• Security keys: create an ed25519-sk key on a YubiKey or similar.
• Password managers: use keys kept in 1Password, Bitwarden or your system agent; the private key never leaves them.
• Host keys: if a server’s host key changed, GitTrail explains it and can replace it when it matches the published one.

More per account

• Edit or rename: every repo using the account updates at once; folder rules and its token follow a rename.
• Delete: repos fall back to their folder rule or the default account. The key file is kept.
• Git settings per account: hooks, templates, pull/push habits or a proxy for every repo of that account.
• Sign-off by default: adds Signed-off-by to this account’s commits.
• Browser profile: links open in the Chrome, Edge, Brave or Firefox profile signed in as this account.
• Token expiry and SSO: see how many days your GitHub token has left, and which organisations need SSO authorisation.