Using one account for all your projects

GitHub recommends using only one user account to manage both personal and professional repositories. Organizations make it easy to contribute to projects for work, open source, and yourself, all from the same account. There’s no need to switch accounts in your browser or manage multiple credentials on the command line!

If you currently have separate accounts for work and personal use, learn how to merge the accounts. Then, continue reading to learn how to make the most of this arrangement.

Publicizing or hiding organization memberships

If you only use one account for all your projects, that account could be a member of multiple organizations. If you don’t want your coworkers to know about your open source affiliations (or vice versa), they don’t have to. Learn how to publicize or hide your organization membership.

Setting your author information per repository

You might want to use different author information for your personal and professional projects. For example, you could use your work email address for professional repositories and your personal email address for other repositories. Learn how to change this author information for each individual repository in “Setting your email address for a single repository.”

Routing notifications

Notifications provide updates about the activities and conversations you’re interested in. If you want notifications about work repositories to go to a different email address than notifications about your own repositories, you can choose the delivery method for each organization you belong to.

Leaving a job

If you use one account for all your GitHub activity, you’ll probably want to continue using that account even after leaving a specific job. To keep your account secure and your contributions intact, follow the steps in “Best practices for leaving your company.”

Private contributions you made while you were a member of an organization can remain in your contributions graph after you leave… but only if you’ve opened an issue or pull request in the repository. This is due to our contribution requirements. You might want to check this before leaving, if you can!

Need help?

Having trouble using one account for all your projects? Let the Support Team know. We’ll be happy to help!

11 Likes

I’m trying to figure out how to move my organization work over to my private account in a way that my contribution graph will remain even if I leave the organization.  (Note that my organization’s repositories are private.) From what I’ve read so far, it sounds like I should

  1. Set my primary, verified email as my work email.

  2. Get added to the organization and work on repositories.

  3. In the event that I leave, 

     a) Delete work email and switch to a verified private email.  At this point, the contributions will not appear in the graph.

     b) Re-add my work email (but do not verify it). At this point, the old contributions associated with that email will appear.

I’ve also read that its necessary to star an organization repository before leaving, but I am not sure how this works if the said repository is private.  Also, this article says that the commits will only remain in the contributions graph if “you’ve opened an issue or pull request in the repository.”

Can someone shed some like on whether the steps I’ve outlined above are sufficient, or if the star-ing and/or issue creating are necessary?  

It would be very useful to support organisation level defaults for this. My org has lots of repos, I have lots of private repos, its a bit error prone to have to remember to set the email address on a project by project basis.

The global gitconfig could have something like this:

[user]
name = Channing Walton
email = channingwalton@mac.com

[user-org]
name = Channing Walton
email = channing.walton@org.com

git could select the email depending on the org the repo is for.