From the course: GitHub Administration Cert Prep

GitHub administration overview - GitHub Tutorial

From the course: GitHub Administration Cert Prep

Start my 1-month free trial Buy for my team

GitHub administration overview

“

- [Instructor] Here we have the GitHub interface, and let's dive into some of the administrative features that you can use when you're looking at the console. First up, you have your profile. So in this icon here, if I select it, I can select my profile, and at this point, it gives me an overview of the ability to edit it. So this is a good place to start when you're controlling your GitHub account, is to put whatever features you'd like inside of here, and you can control this from this icon. Now, notice as well from the README file, this is a special feature of GitHub. You can also edit this as marked down, and this is a great way to have a more robust profile. If we go back here as well, we can look at repositories. This is one of the key features that you can administer, and inside of here, you could select new for a new repository. You could also search for your existing repositories as well. So this is a administrative feature that you get from a single user account. Now, if we go down to projects, you can also administer projects. You can also administer codespaces. Let's go ahead and take a look at that real quick. If we go to codespaces here and you say new codespace, we can actually pick a repository for the codespace to be administered inside of. We also could administer a new codespace as well, and that's where we would select the different kinds of codespace types from GPU to CPU. If we scroll down here later, we can also look at organization. So organizational level shows us the different things that we have here. So we have organizations that I belong to. I also have the ability to have ownership privileges. So in this particular organization, for example, if I go into it, you can see that I can pin repositories onto the organization. I also have a huge list of repositories as well. There's over a thousand repositories, and I also have teams that I can administer and people. So the organization is a higher level entity that is beyond just the reach of a single user, like a individual GitHub account, and it gives us more organizational control. We also could go into the settings here and set up things like billing, for example, or repository roles, member privileges, moderation, requests from users, et cetera, and even get into features like copilot, for example would we want to enable certain restrictions or features with copilot. Also, we configure actions, webhooks, discussions, packages, pages, et cetera. So really there's a much more rich interface when you get into an organizational level because you have team level privileges and organizational level privileges that can be propagated across the entire organization, not just your individual account.

Contents