Tip: If you require more granular read/write access to a repository owned by your user account, consider transferring the repository to an organization. For more information, see "Transferring a 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:
- Invite collaborators
- Change the visibility of the repository (from public to private, or from private to public)
- Limit interactions with a repository
- Merge a pull request on a protected branch, even if there are no approving reviews
- Delete the repository
- Manage a repository's topics
- Manage security and analysis settings. For more information, see "Managing security and analysis settings for your user account."
- Enable the dependency graph for a private repository
- Delete packages. For more information, see "Deleting a package."
- Create and edit repository social cards. For more information, see "Customizing your repository's social media preview."
- Make the repository a template. For more information, see "Creating a template repository."
- Receive GitHub Dependabot alerts for vulnerable dependencies in a repository.
- Dismiss GitHub Dependabot alerts in your repository. For more information, see "Viewing and updating vulnerable dependencies in your repository."
- Manage data usage for your private repository
- Define code owners for the repository
- Archive repositories
- Create security advisories. For more information, see "About GitHub Security Advisories."
- Display a sponsor button. For more information, see "Displaying a sponsor button in your repository."
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
Note: 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 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
- Apply suggested changes to pull requests. For more information, see "Incorporating feedback in your pull request."
- Send pull requests from forks of the repository
- Publish, view, and install packages. For more information, see "Publishing and managing packages."
- Create and edit Wikis
- Create and edit releases. For more information, see "Managing releases in a repository.
- 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."
- Report abusive content to GitHub Support or GitHub Premium Support. For more information, see "Reporting abuse or spam."
- Transfer an issue to a different repository. For more information, see "Transferring an issue to another repository."