Permission levels for a user account repository

Owner access on a repository owned by a user account

The repository owner has full control of the repository. In addition to all the permissions allowed by repository collaborators, the repository owner can:

• Add collaborators

• Change the visibility of the repository (from public to private, or from private to public)

• Merge a pull request on a protected branch, even if there are no approved reviews

• Delete the repository

• Manage a repository's topics

• Define code owners for the repository

• Archive repositories

There is only one owner of a repository owned by a user account; this permission cannot be shared with another user account. To transfer ownership of a repository to another user, see "How to transfer a repository."

Collaborator access on a repository owned by a user account

Collaborators on a personal repository can:

• Push to (write), pull from (read), and fork (copy) the repository

• Create, apply, and delete labels and milestones

• Open, close, re-open, and assign issues

• Edit and delete comments on commits, pull requests, and issues

• Mark an issue or pull request as a duplicate. For more information, see "About duplicate issues and pull requests."

• Open, merge and close pull requests

• Send pull requests from forks of the repository

• Create and edit Wikis

• Create and edit Releases

• Remove themselves as collaborators on the repository

• Submit a review on a pull request that will affect its mergeability

• Act as a designated code owner for the repository. For more information, see "About code owners."

• Lock a conversation. For more information, see "Locking conversations."

Further reading

• "Inviting collaborators to a personal repository"
• "Repository permission levels for an organization"