Conseil
If you require more granular access to a repository owned by your personal account, consider transferring the repository to an organization. For more information, see Transfert d’un dépôt.
Owner access for a repository owned by a personal account
Repositories owned by personal accounts have a single owner who has full control of the repository. In addition to the actions that any collaborator can perform, the repository owner can perform the following actions.
Collaborator access for a repository owned by a personal account
Collaborators on a personal repository can pull (read) the contents of the repository and push (write) changes to the repository.
Remarque
In a private repository, repository owners can only grant write access to collaborators. Collaborators can't have read-only access to repositories owned by a personal account.
Collaborators can also perform the following actions.
| Action | More information |
|---|---|
| Fork the repository | À propos des duplications (fork) |
| Rename a branch other than the default branch | Changement du nom d’une branche |
| Create, edit, and delete comments on commits, pull requests, and issues in the repository | |
| Create, assign, close, and re-open issues in the repository | Documentation GitHub Issues |
| Manage labels for issues and pull requests in the repository | Gestion des étiquettes |
| Manage milestones for issues and pull requests in the repository | Création et modification de jalons pour les problèmes et les demandes de tirage |
| Mark an issue or pull request in the repository as a duplicate | Marquage de problèmes ou de demandes de tirage comme doublons |
| Create, merge, and close pull requests in the repository | Propositions de modifications de votre travail avec des demandes de tirage |
| Enable and disable auto-merge for a pull request | Fusion automatique d'une demande de tirage |
| Apply suggested changes to pull requests in the repository | Incorporation de commentaires dans votre demande de tirage |
| Create a pull request from a fork of the repository | Création d’une demande de tirage à partir d’une duplication |
| Submit a review on a pull request that affects the mergeability of the pull request | Révision des changements proposés dans une demande de tirage |
| Create and edit a wiki for the repository | À propos des wikis |
| Create and edit releases for the repository | Gestion des mises en production dans un référentiel |
| Act as a code owner for the repository | À propos des propriétaires de code |
| Remove themselves as collaborators on the repository | Removing yourself from a collaborator's repository |
If you want more granular control of repository permissions, you can create a repository within an organization. For more information, see Autorisations d’accès sur GitHub.
Access after removing a collaborator
While forks of private repositories are deleted when a collaborator is removed, the person will still retain any local clones of your repository.
When you remove a collaborator from your project, they lose read/write access to your repository. If the repository is private and the person has created a fork, then that fork is also deleted.
Next steps
To learn how to add collaborators to your personal repository, see Inviting collaborators to a personal repository.