GitHub

GitHub is used for version control. The paid Team plan is a great plan to start with. Upon creation of an organization for your company, a number of "seats" will have to be purchased for every person who needs access to GitHub. Once that is done, a number of teams should be created to manage access.

Manage access

It is important that access is properly set up for your GitHub organization. This can prevent unqualified users from accidentally making a mistake that could lead to confusion and unnecessary downtime.

The following teams should be created, along with the roles prescribed:

admin

Admin users, typically in the form of engineering management, who have the role of `Admin`

back-end

Back-end engineers which has the role of `Write` for all back-end **and** front-end repos

front-end

Front-end engineers which has the role of `Write` for all front-end repos

product

Members of the Product team which has have the role of `Read`

QA

Members of the QA team which has the role of `Write`

New Repo Setup

When setting up a new repo, the followed conventions should be adhered to:

• All front-end repos should have the -static suffix, ie dashboard-static.
• All back-end API repos should have the -api suffix, ie foo-api.