提示
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 转让仓库.
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.
| Action | More information |
|---|---|
| Add collaborators | Inviting collaborators to a personal repository |
| Change the visibility of the repository | 设置存储库可见性 |
| Rename a branch, including the default branch | 重命名分支 |
| Merge a pull request on a protected branch, even if there are no approving reviews | 关于受保护分支 |
| Delete the repository | 删除仓库 |
| Manage the repository's topics | 使用主题对仓库分类 |
| Delete and restore packages | 删除和恢复包 |
| Customize the repository's social media preview | 自定义仓库的社交媒体预览 |
| Create a template from the repository | 创建模板仓库 |
| Control access to Dependabot alerts | 管理存储库的安全和分析设置 |
| Define code owners for the repository | 关于代码所有者 |
| Archive the repository | 存档仓库 |
| Allow or disallow auto-merge for pull requests | 管理仓库中拉取请求的自动合并 |
| Manage deploy keys | 管理部署密钥 |
| Manage webhooks | 关于 web 挂钩 |
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.
注意
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 | 关于分叉 |
| Rename a branch other than the default branch | 重命名分支 |
| Create, edit, and delete comments on commits, pull requests, and issues in the repository | |
| Create, assign, close, and re-open issues in the repository | GitHub Issues 文档 |
| Manage labels for issues and pull requests in the repository | 管理标签 |
| Manage milestones for issues and pull requests in the repository | 创建和编辑议题及拉取请求的里程碑 |
| Mark an issue or pull request in the repository as a duplicate | 将议题或拉取请求标记为重复 |
| Create, merge, and close pull requests in the repository | 通过拉取请求提议工作更改 |
| Enable and disable auto-merge for a pull request | 自动合并拉取请求 |
| Apply suggested changes to pull requests in the repository | 在拉取请求中加入反馈 |
| Create a pull request from a fork of the repository | 从复刻创建拉取请求 |
| Submit a review on a pull request that affects the mergeability of the pull request | 审查拉取请求中的建议更改 |
| Create and edit a wiki for the repository | 关于 wikis |
| Create and edit releases for the repository | 管理仓库中的发行版 |
| Act as a code owner for the repository | 关于代码所有者 |
| 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 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.