Случайно форкнул проект в GitHub, как теперь его удалить?
Случайно форкнул проект в GitHub. Проект x64dbg. Удалил у себя все файлы, но каталог master x64dbg остался. Как от него избавиться? И желательно от истории тоже.
Отслеживать
13.7k 12 12 золотых знаков 43 43 серебряных знака 75 75 бронзовых знаков
задан 10 сен 2015 в 1:38
user188653 user188653
2 ответа 2
Сортировка: Сброс на вариант по умолчанию
Форк — это самостоятельный репозиторий на GitHub, он создается для того, чтобы вы могли продолжить работу над проектом, сохранили всю историю изменений до форка и могли делать пулл-реквесты.
Если вам нужно только получить последнюю версию проекта, то форк для этого не нужен. Можно клонировать «родительский» репозиторий, причём достаточно будет неполного (неглубокого) клонирования.
Чтобы полностью удалить любой проект на GitHub (не обязательно форк):
- Перейдите на страницу проекта (репозитория).
- В правой части экрана нажмите на вкладку Settings в виде шестерёнки.
- В разделе Danger zone нажмите Delete this repository
- В текстовое поле введите полное название вашего репозитория
- Нажмите кнопку под текстовым полем для подтверждения.
Удаление репозитория
Вы можете удалить любой репозиторий или вилку, если вы являетесь владельцем организации или имеете права администратора для репозитория или вилки. При удалении репозитория, в котором создана вилка, вышестоящий репозиторий не удаляется.
Only members with owner privileges for an organization or admin privileges for a repository can delete an organization repository. If Allow members to delete or transfer repositories for this organization has been disabled, only organization owners can delete organization repositories. For more information, see «Repository roles for an organization.»
Deleting a public repository will not delete any forks of the repository.
Warnings:
- Deleting a repository will permanently delete release attachments and team permissions. This action cannot be undone.
- Deleting a private repository will delete all forks of the repository.
Some deleted repositories can be restored within 90 days of deletion. For more information, see «Restoring a deleted repository.»
- On GitHub.com, navigate to the main page of the repository.
- Under your repository name, click
Settings. If you cannot see the «Settings» tab, select the
dropdown menu, then click Settings.
Что происходит с вилками при удалении репозитория или изменении видимости?
Удаление репозитория или изменение его видимости влияет на вилки этого репозитория.
Warning:
- If you remove a person’s access to a private repository, any of their forks of that private repository are deleted. Local clones of the private repository are retained. If a team’s access to a private repository is revoked or a team with access to a private repository is deleted, and team members do not have access to the repository through another team, private forks of the repository will be deleted.
- You are responsible for ensuring that people who have lost access to a repository delete any confidential information or intellectual property.
- People with admin permissions to a private or internal repository can disallow forking of that repository, and organization owners can disallow forking of any private or internal repository in an organization. For more information, see «Managing the forking policy for your organization» and «Managing the forking policy for your repository.»
Deleting a private repository
When you delete a private repository, all of its private forks are also deleted.
Private forks and permissions
Private forks inherit the permissions structure of the upstream repository. This helps owners of private repositories maintain control over their code. For example, if the upstream repository is private and gives read/write access to a team, then the same team will have read/write access to any forks of the private upstream repository. Only team permissions (not individual permissions) are inherited by private forks.
Note: When you change base permissions for an organization, permissions for private forks are not automatically updated. For more information, see «Setting base permissions for an organization.»
Changing the visibility of an internal repository
If the policy for your enterprise permits forking, any fork of an internal repository will be private. If you change the visibility of an internal repository, any fork owned by an organization or personal account will remain private.
Deleting the internal repository
If you change the visibility of an internal repository and then delete the repository, the forks will continue to exist in a separate network.
Further reading
- «Setting repository visibility»
- «About forks»
- «Managing the forking policy for your repository»
- «Managing the forking policy for your organization»
- «Enforcing repository management policies in your enterprise»
Удаление файлов в репозитории
Вы можете удалить отдельный файл или весь каталог в репозитории на GitHub.
Кто может использовать эту функцию.
People with write permissions can delete files or directories in a repository.
About file and directory deletion
You can delete an individual file in your repository or an entire directory, including all the files in the directory.
If you try to delete a file or directory in a repository that you don’t have write permissions to, we’ll fork the project to your personal account and help you send a pull request to the original repository after you commit your change. For more information, see «About pull requests.»
If the file or directory you deleted contains sensitive data, the data will still be available in the repository’s Git history. To completely remove the file from GitHub, you must remove the file from your repository’s history. For more information, see «Removing sensitive data from a repository.»
Deleting a file
- Browse to the file in your repository that you want to delete.
- In the top-right corner, select the
dropdown menu, then click Delete file.
Below the commit message fields, decide whether to add your commit to the current branch or to a new branch. If your current branch is the default branch, you should choose to create a new branch for your commit and then create a pull request. For more information, see «Creating a pull request.»
Deleting a directory
- Browse to the directory in your repository that you want to delete.
- In the top-right corner, select the
dropdown menu, then click Delete directory.
Below the commit message fields, decide whether to add your commit to the current branch or to a new branch. If your current branch is the default branch, you should choose to create a new branch for your commit and then create a pull request. For more information, see «Creating a pull request.»