I called this "Github Operative System" because this small meta-guide's intent is not so much to describe Github usage in great detail but to provide the reader a method or a system indeed to "operate" on a project professionally, in a teamwork context.
<aside> 💡 Github docs - link
</aside>
Github account is personal, you should not use your company mail.
Moreover a lot of services lets you login with Github and if you already have accounts created this way, you will have to logout from your company account and login with yours, then log back with the company one... a little messy.
"Organization" is the way Github handles this problem and spare us the pain of having 2 different accounts.
Anyway if you used your company mail you can always change it from settings > email
But every time you change the mail you will loose all the history of your work. (it's bad for you)
When invited in our "Organization" you will be asked to activate 2FA (2 factor authentication) for security reasons. settings > security
creation: a company designed git manager will create the repo for you. You will decide the name together. If the name has more than one word, it will have hyphens, something like my-project-web.
If a monorepo structure makes sense for the project, it will be decided at this moment.