[{"content":" This article focuses on managing multiple Git accounts with SSH.\nThere are plenty of guides on handling multiple Git accounts, but many are fragmented or only solve part of the problem. Here’s a streamlined summary for practical use.\nCommon scenarios include:\nUsing different SSH keys for different domains Using different SSH keys for the same domain Using different Git accounts for the same domain Ultimately, there are two main challenges:\nSwitching SSH keys with the SSH client Switching Git accounts with the Git client In most cases (about 90%), simply using different SSH keys is enough. The Git account identity (username <username@domain>) is usually less critical.\nSSH Account Configuration For SSH basics, see GitHub’s official docs.\nThe most common approach is to use the Host directive in your ~\/.ssh\/config to specify different keys:\nHost github.dev HostName github.com IdentityFile ~\/.ssh\/github_rsa IdentitiesOnly yes Host gitlab.yourdomain.com IdentityFile ~\/.ssh\/gitlab_rsa IdentitiesOnly yes This lets you use different SSH keys for different repos, even with the same Git account.\nGit Account Configuration Why do this?\nCompanies often use private Git servers with domain accounts You may want to separate personal and work accounts on GitHub You can have Git use different accounts per workspace using git config includes:\n[includeIf "gitdir:~\/workspace_github\/"] path = ~\/.gitconfig-github [includeIf "gitdir:~\/workspace_gitlab\/"] path = ~\/.gitconfig-gitlab [includeIf "gitdir:~\/workspace_work\/"] path = ~\/.gitconfig-work [filter "lfs"] required = true clean = git-lfs clean -- %f smudge = git-lfs smudge -- %f process = git-lfs filter-process [init] defaultBranch = main [core] symlinks = true ignorecase = false [pull] rebase = true Each ~\/.gitconfig-xxx just sets your name, email, and optionally a signing key:\n[user] name = github_username email = github_username@github.com signingkey = <YOUR_GPG_KEY_ID> [init] defaultBranch = main [commit] gpgsign = true With this, you’ll use the right Git identity in each workspace.\nCombine this with your SSH config. Test with ssh -T git@github.dev.\nFor example, to use two GitHub accounts with different SSH keys, just replace github.com with your custom host (e.g., github.dev) when cloning:\ngit clone git@github.dev:user\/repo.git\nBonus: Custom git Wrapper To automate domain switching, here’s a simple wrapper script. It checks your current directory and rewrites the clone URL if needed:\n#!\/bin\/bash REAL_GIT="\/usr\/local\/bin\/git" if [[ "$1" == "clone" ]]; then current_dir=$(pwd) if [[ "$current_dir" == \/Users\/<your_username>\/workspace_github* ]]; then shift for arg in "$@"; do if [[ "$arg" =~ ^git@github\\.com: ]]; then new_url="${arg\/git@github.com:\/git@github.dev:}" echo "[git wrapper] Replacing clone URL with: $new_url" exec "$REAL_GIT" clone "$new_url" fi done fi fi exec "$REAL_GIT" "$@" ","permalink":"https:\/\/genffy.com\/en\/posts\/202504\/git-multi-account-manage\/","summary":"
\n

This article focuses on managing multiple Git accounts with SSH.<\/p><\/blockquote>\n

There are plenty of guides on handling multiple Git accounts, but many are fragmented or only solve part of the problem. Here’s a streamlined summary for practical use.<\/p>\n

Common scenarios include:<\/p>\n