From the course: GitHub Foundations Cert Prep by Microsoft Press

Unlock this course with a free trial

Join today to access over 25,500 courses taught by industry experts.

Recognize repository permission levels

Recognize repository permission levels - GitHub Tutorial

From the course: GitHub Foundations Cert Prep by Microsoft Press

Start my 1-month free trial Buy for my team

Recognize repository permission levels

“

- [Instructor] Now I scratch my head a little bit on this. I don't know about you or anybody else. I wish it were a bit more intuitive in GitHub Web to see and check what our permission role is. It is flexible; it's going to depend upon where you are and what you're governed by. We've known the various levels. Ultimately, at the ground level, there's the repository, and the actions are things like pushing code, managing settings. In other words, separation of duties between code, work, or being a contributor, and being a repo maintainer. We've talked about that before. One thing is attempt actions; if you don't see the control, you don't have a permission. That's kind of low tech though. You always can go into your settings and look at Manage Access. Again, if you can get into settings in the repo, the impact here is pretty straightforward. We've covered this to date. Read and triage are ways to give permissions. Read would be the normal default, everyone permission 80% of the time…

Contents