SSH, Actually 100% signal, 0% noise.

The git@ Username

concept
depth 2/2 − deeper + surface

The username in [email protected] and [email protected] is always git—for everyone. The service doesn't care about your account username; it cares about which SSH key you presented. Your actual identity comes from the key, not the username.

The pieces:

  • The service doesn't care about your GitHub username
  • It cares about which SSH key you presented
  • The SSH key is linked to your account
  • The git user is just a convention

You can watch the key-to-identity lookup happen:

ssh -T [email protected]
# → Hi username! You've successfully authenticated...

You typed git; the greeting names you—because the key you presented is registered to your account.

One consequence trips up almost everyone eventually: since the username and hostname are identical for every account on the service, the key is the only thing that distinguishes two accounts. That's the trap behind multi-account setups—and why the fix (host aliases) works by changing which key gets presented, not the username.