Esta versión de GitHub Enterprise se discontinuó el 2021-06-09. No se realizarán lanzamientos de patch, ni siquiera para problemas de seguridad críticos. Para obtener un mejor desempeño, más seguridad y nuevas características, actualiza a la última versión de GitHub Enterprise. Para obtener ayuda con la actualización, contacta al soporte de GitHub Enterprise.

Permission levels for a user account repository

A repository owned by a user account has two permission levels: the repository owner and collaborators.

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:

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
  • 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."
  • Transfer an issue to a different repository. For more information, see "Transferring an issue to another repository."

Further reading