Yes — if the accounts are legitimate; no — if you're stacking free personal accounts. GitHub's Terms of Service allow one person no more than one free account (plus one free machine account for automation). A second account is normal and officially supported when it is an employer-created enterprise/managed account, a service account, or a paid account — GitHub's own documentation teaches how to switch between such accounts on one computer. Several free personal accounts for the same person violate the ToS; GitHub asks you to merge them. This page states exactly where the line is — and what tooling to use once you're on the right side of it.
What GitHub's Terms of Service actually say
From Account Requirements (docs.github.com site-policy), the short version: "you may not have more than one free Account." The full rules:
- "One person or legal entity may maintain no more than one free Account (if you choose to control a machine account as well, that's fine, but it can only be used for running a machine)."
- "Your login may only be used by one person — i.e., a single login may not be shared by multiple people."
- Accounts are created by humans; bot accounts aren't allowed — one human-operated machine account for automation is.
Supporting pages say it plainly: the Education docs state "It is against the GitHub Terms of Service to maintain more than one individual account," and the account-types page advises people with several self-created personal accounts to combine them. Meanwhile the account-management docs describe switching between multiple accounts — because the legitimate cases are real: a personal account plus an employer-managed enterprise account, or a service account.
Allowed or not? Every common scenario
| Scenario | Verdict | Rule involved |
|---|---|---|
| One personal account (free or Pro) | ✅ Allowed — the recommended default | One account, any number of organizations |
| Personal account + employer-created enterprise/managed account | ✅ Allowed — the officially documented multi-account case | Managed accounts exist for this; docs teach switching |
| Personal account + service account | ✅ Allowed | Service accounts are an enterprise feature GitHub documents |
| Free personal + one free machine account (automation) | ✅ Allowed | Explicitly permitted in the ToS |
| Two paid accounts (different businesses/clients) | ✅ Allowed | The restriction targets free accounts |
| Two or more free personal accounts, same person | ❌ Not allowed | "No more than one free Account" — merge them |
| Second free account to farm education/student benefits | ❌ Not allowed | Education docs call it a ToS violation |
| Sharing one login among multiple people | ❌ Not allowed | Logins are single-person; use organization seats |
What actually happens when rules are broken
- Duplicate free personal accounts: GitHub requests a merge; discovered education benefits are revoked. Merging is the fix, not a ban (unless there's abuse).
- Abuse patterns — spam, ban-evasion, automation abuse: suspension of linked accounts. This is what enforcement is built for.
- Legitimate multi-account work (personal + enterprise/service/paid) on one machine: no enforcement concern — the ToS says nothing about clients or machines, only about account validity.
Already have two free personal accounts?
- Choose the account that keeps your identity, repositories, and paid features.
- Use GitHub's account merging flow to move repositories and history into it.
- Re-attach your email addresses to the retained account so contribution attribution stays correct.
- For the accounts you legitimately maintain afterwards (work + personal, service, machine), set up proper multi-account tooling — see the next section.
On the right side of the rules? Use tooling built for it
Once your accounts are legitimate (enterprise-managed, service, machine, paid), the remaining problem is practical: Git and desktop clients on one PC default to single-account behavior. Three levels of solution exist:
- Git-level configuration — one SSH key per account, per-repository HTTPS credentials, folder-based identities via
includeIf. Full commands in our guide How to Set Up Multiple GitHub Accounts on One Computer. - CLI — the GitHub CLI keeps multiple logins (
gh auth switch). - GUI — GITmaxed — the Windows client for exactly this situation: every allowed account signed in at the same time, each repository pinned to its account, every push authenticated as the right identity. No sign-out dance, no credential config. It doesn't bend GitHub's rules — it respects them and removes the friction of using what you're entitled to.
Related questions answered (the same queries, one by one)
Can I have 2 GitHub accounts on one computer?
Yes, when both are legitimate (personal + enterprise/service/paid). Use per-repository credentials or GITmaxed to keep them separated.
Is it against GitHub ToS to have multiple accounts?
Against the ToS: multiple free personal accounts for one person. Not against it: enterprise/managed, service, machine, and paid accounts — GitHub documents managing those.
Can I create a second GitHub account?
You can create one free personal account. A second free personal account for yourself is what the ToS prohibits — a second account should be enterprise, service, machine, or paid.
Will GitHub ban me for having multiple accounts?
Not for legitimate multi-account use. Enforcement targets duplicate free accounts (merge requested) and abuse (suspension).
Can two GitHub accounts use the same email?
No — each account needs its own primary email.
Can I use two GitHub accounts with GitHub Desktop?
Official GitHub Desktop signs into one GitHub.com account. For two allowed accounts in one desktop client, use GITmaxed — see our GitHub Desktop multiple accounts page.
Does GitHub allow a work account and a personal account?
Yes — that's the documented multi-account case. Keep credentials separate per repository and you're fully compliant.
No comments:
Post a Comment