-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Work Email Registration #8
Comments
Agreed. This is how I set my account up. |
Also, the former is technically against the GitHub Terms of Service:
https://help.github.com/articles/github-terms-of-service/#3-account-requirements (Also, 👋 from a new developer under Census!) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Regarding:
"You must register with your work email, which should be independent from any personal account you may have on Github."
From @benbalter:
"We actually suggest the opposite in the best-practices peer group. (https://government-community.githubapp.com/government/best-practices/blob/master/docs/account-management.md#requiring-users-to-establish-purpose-specific-accounts) Beyond making things harder for developers in terms of Git configuration and SSH keys, unlike say, Twitter, where it’s normal to have multiple accounts, GitHub allows you to have multiple email addresses, and be associated with multiple organizations, automatically disambiguating your use, depending on what context your in.
You may also want to clarify the difference between an organization account and an individual account. Humans should have one user account, bureaus should have an organization account (which you will need a user account to create), of which that user is a member.
The text was updated successfully, but these errors were encountered: