팁
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 | 웹후크 정보 |
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 | 위키 정보 |
| 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.