Account setup and multi-account handling

Purpose

Commits land under the right identity, and personal/work accounts don't collide on Windows.

The standard

• Work commits use your work GitHub account and work email. Personal accounts are not members of the org.

• SSH keys for WSL; HTTPS + Git Credential Manager on Windows. One key per machine, named <user>@<machine>.

• Signed commits (SSH signing) are [TEAM: required / recommended].

• Org membership requires MFA.

Procedure — WSL

1. ssh-keygen -t ed25519 -C "you@work.com"; add the public key to GitHub → Settings → SSH keys.

2. git config --global user.name "…" and user.email "…" with the work email.

3. If you also use a personal account on the same machine, use a per-directory identity: in ~/.gitconfig add [includeIf "gitdir:~/work/"] path = ~/.gitconfig-work.

4. Test: ssh -T git@github.com.

Procedure — Windows credential conflicts

1. Control Panel → Credential Manager → Windows Credentials → remove stale git:https://github.com entries.

2. Next push prompts for login; sign in with the work account.

3. For two accounts on Windows, set git config --global credential.useHttpPath true so credentials are stored per repo URL.

Anti-patterns

Committing from a personal identity into work repos; sharing a deploy key across machines.

Owner: [TEAM] · Last reviewed: 2026-09