ヒント
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 | webhook について |
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 | Issue とプルリクエストのマイルストーンの作成と削除 |
| Mark an issue or pull request in the repository as a duplicate | Issue またはPull Requestを重複としてマークする。 |
| Create, merge, and close pull requests in the repository | pull request を使用して作業に対する変更を提案する |
| 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 | ウィキについて |
| 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.