<p>You don’t really <em>get</em> Git until you try running two (or more) GitHub accounts on the same machine.</p>
<p>That’s when you find out what’s really going on with:</p>
<ul>
<li><code>~/.ssh/config</code></li>
<li><code>~/.gitconfig</code></li>
<li>Config overrides</li>
<li>Folder-specific rules</li>
</ul>
<p>At first, it feels like “just a quick config,” but pretty soon you’re deep into:</p>
<ul>
<li>How Git decides which config to use</li>
<li>How SSH knows which key to load</li>
<li>What <code>includeIf</code> and <code>insteadOf</code> actually do</li>
<li>Why <code>IdentitiesOnly</code> can save you from using the wrong key</li>
</ul>
<p>Once you nail this setup, pushing to the wrong account becomes almost impossible.</p>
<hr>
<h3>Step 1 — Create separate SSH keys</h3>
<ul>
<li><strong>Personal:</strong> <code>~/.ssh/id_ed25519</code></li>
<li><strong>Work:</strong> <code>~/.ssh/id_ed25519_company</code></li>
</ul>
<p>Add them to your SSH agent so you’re not typing passphrases all day.</p>
<hr>
<h3>Step 2 — SSH config (<code>~/.ssh/config</code>)</h3>
<pre><code class="language-ssh">Host github.com
  IdentityFile ~/.ssh/id_ed25519
  IdentitiesOnly yes

Host github-company
  IdentityFile ~/.ssh/id_ed25519_company
  IdentitiesOnly yes
</code></pre>
<p>This makes sure each account always uses the right key.</p>
<hr>
<h3>Step 3 — Main Git config (<code>~/.gitconfig</code>)</h3>
<p>Keep your personal details as the default, and use <code>includeIf</code> to load work settings only for certain folders:</p>
<pre><code class="language-ini"><span class="hljs-section">[includeIf &quot;gitdir:~/work-projects/&quot;]</span>
  <span class="hljs-attr">path</span> = ~/.gitconfig-company
</code></pre>
<hr>
<h3>Step 4 — Work Git config (<code>~/.gitconfig-company</code>)</h3>
<p>Set your company name/email, and rewrite GitHub URLs so work repos automatically use the right SSH alias:</p>
<pre><code class="language-ini"><span class="hljs-section">[url &quot;git@github-company:&quot;]</span>
  <span class="hljs-attr">insteadOf</span> = git@github.com:
  <span class="hljs-attr">insteadOf</span> = https://github.com/
</code></pre>
<hr>
<h3>Step 5 — Organize by folders</h3>
<ul>
<li><code>~/personal-projects/</code> → personal account</li>
<li><code>~/work-projects/</code> → work account</li>
</ul>
<p>Now you just clone normally — Git and SSH handle the rest. No more manual switching, no more mistakes. 🚀</p>


Jobs is a daily dev squad dedicated to sharing job opportunities, career advice, and community-driven insights for developers across all tech stacks, helping them grow and succeed in the industry.

Jobs

Managing multiple GitHub accounts on one machine requires proper SSH key configuration and Git settings. The setup involves creating separate SSH keys for each account, configuring SSH hosts with specific identity files, using Git's includeIf directive for folder-specific configurations, and organizing projects by directories. This approach prevents accidentally pushing to the wrong account and automates the switching between personal and work repositories.

Multiple GitHub Accounts — A Must-Have Skill for Developers

<p>I could have used this post 2 months ago.</p>
<p>This is pretty much exactly the same setup that I ended up at when I was setting up my new work computer.</p>


<p>i was on the same scenario and created a very simple CLI tool to manage profiles. Unfortunately, did not gather enoguh users to test and therefore check possible errors or areas for improvement <a href="https://github.com/GuilleAmutio/gitp" target="_blank" rel="noopener nofollow">https://github.com/GuilleAmutio/gitp</a></p>


<p>I see the point, but I don’t understand why should I do that</p>


<p>I need to test this one. All others articles I read on this subject were misleading at beast.
Maybe one thing missing: how to handle 2 accounts (if possible) on your favorite IDE…</p>


<p>You saved a lot of my time. Thanks for sharing. I was plucking my hair with this config. Though my requirements is little bit complex but, it’s a good start.</p>
