Repository Access
+Last updated on 2025-01-09 | + + Edit this page
+ + + +Overview
+Questions
+- What levels of repository permissions are there? +
Objectives
+- Know how to give a collaborator access to your repository. +
To be able to contribute to the git-training-demo
+repository your instructors will have to give you access. They are going
+to showcase this now. The steps are:
In the repository page on GitHub, click the “Settings” button on the +right, select “Collaborators”, click “Add people”, and enter a +username/s.
+To accept access to the repository, you will need to go to https://github.com/notifications +or check for an email notification. Once there you can accept access to +the repository.
+Permission Levels
+Personal Repositories
+Repositories on personal accounts only have two levels of +permissions, the Owner and Collaborators1. To use the branching +model in this lesson you would need adding as a collaborator. You can +still contribute to a public repository without being added as a +collaborator by using the forking model.
+Organisational Repositories
+Repositories in organisations have more levels of permissions2. Team +members require at least write access to use the +branching model. For all lower levels of access use the forking +model.
+Key Points
+- On a repository you own or are an admin on navigate to
https://github.com/<organisation>/<repository>/settings/access
+to control access for collaborators.
+ - You can give individuals or teams access to a repository. +
The GitHub +documentation has more information on permissions for a repository +on a personal account.↩︎
+The GitHub +Documentation has more information on the different permission +levels for repositories in organisations.↩︎
+