> GitHub recommends using only one user account to manage both personal and professional repositories.

https://github.community/t/using-one-account-for-all-your-pr...

Of course they do. That doesn't make it a good idea though.

Where I'm contracting now didn't want my account added to their org because it's not a profile picture of me. As the public facing stuff of the account is my personal stuff, I don't want someone else to tell me how it should be. So a new account for this customer it is..

We actually discussed this for quite a while at work when I pushed us to start contributing to open-source. Mostly it came down to the fact that TfL wished me to keep my work-life and personal-life separate to keep things simple. Reading that back, it doesn't sound so crazy.

GitHub wants a lot of silly things. I want a lot of silly things. Doesn't mean we all get what we want.

I wish they didn’t do that. Or preferably, I wish they had native “containers” for work and personal repos.

Explore is one of my favorite features and now it’s crowded with work related suggestions. It makes it harder to separate the personal/professional persona and interests. This problem also manifests in notifications. I want a clear separation so I can focus on my personal life after work.

I’ve thought many times about creating a separate account.

Be careful. If you ever write a commit for an open source project a disgruntled employer could become ideas, depending on your contract.

Do you use windows? I found that having multiple GitHub account is infuriating on windows because it forces you to go into an obscure security manager to delete a record in order to switch which account your using. Never found a way around it.

I had never heard of this so I just tried to reproduce this - I have no trouble logging into two separate GitHub accounts in different Chrome profiles. What makes Firefox profiles different?

I think he means when using git from the command line. Trying to push to your repo will trigger a github sign in process, which will then save the credentials to Windows Credential Manager. Git will then ALWAYS use those from that point on credentials unless you go into the manager and delete them, which is a massive pain if you use multiple github accounts.

I think he's talking about the windows credential manager for HTTPS authorization for cloning/pushing.

Aha! I've always just used SSH authorization with GitHub.

Oh, I'll give that a try, thanks!