Introduction to GitHub Administration
1. Introduction to GitHub Administration
Welcome to the video on GitHub Administration! We’ll cover how to manage access at the organization, team, and repository levels to keep your projects secure and efficient. Let's dive in!2. What is a GitHub Organization?
A GitHub Organization is a centralized workspace where we manage multiple projects efficiently. It provides role-based access, ensures users have the proper permissions and enforces security policies to protect our data.3. Creating a GitHub Organization
To create a GitHub organization, click on your profile icon in the upper right corner and select "Your organizations." Then, select "New organization" and choose a plan that fits our needs. Next, we'll fill in our organization's details and contact information to complete the setup. We'll focus on the capabilities of the Enterprise Cloud option, but if you want more information on the different GitHub plans, check out the linked article.4. Meet DataCamp-Marketplace
We’ve created the DataCamp-Marketplace organization. Stan is the Owner with full control, and several colleagues have been invited and given Member roles. We also have one Outside Collaborator with limited access to specific repositories.5. Administration at organization level
In GitHub organizations, roles define access and responsibilities. Owners have full control, Members collaborate with standard permissions, and Outside Collaborators have limited access to specific repositories. Additional roles include: Moderators managing interactions in public repositories. Billing Managers, who handle billing. Security Managers, overseeing security settings. GitHub Enterprise Cloud offers even more flexibility with custom roles.6. Managing Teams
Teams in a GitHub organization are essential for streamlining collaboration. By grouping users into teams, we can easily manage permissions and organize our projects. Owners and Members can create and organize teams, grouping them by project, role, or department. Nested teams allow the mirroring of internal hierarchies, such as a data team with sub-teams like data engineers and data scientists. This setup ensures clear delegation.7. Administration at team level
Team Members work on projects, while Team Maintainers manage settings and members. For easier management, assign permissions to teams rather than individuals. For example, instead of granting each Data Scientist separate access, assign it to the entire Data team.8. Administration at repository level
Lastly, let's recall repository roles. From least to most access: Read: viewing and discussing the project. Triage: managing issues and pull requests. Write: actively pushing code. Maintain: managing the repository without sensitive actions. Admin: full control, including security management and deletion. Assign roles that fit each person's or team's function to provide just the right access.9. Error Reminder
Remember, if our colleague sends us a link to a repository and you see a 404 error instead, it means we don’t have the right access.10. Let's practice!
We’ve explored GitHub administration, including access levels for organizations, teams, and repositories. Now, let’s put what we’ve learned into practice!Create Your Free Account
or
By continuing, you accept our Terms of Use, our Privacy Policy and that your data is stored in the USA.