@@ -36,6 +36,8 @@ You can also rename the default branch. For more information, see "[AUTOTITLE](/
|
||||
|
||||
To change the default branch, your repository must have more than one branch. For more information, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository#creating-a-branch)."
|
||||
|
||||
Additionally, you need to have admin access to a repository to change the default branch.
|
||||
|
||||
## Changing the default branch
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
|
||||
@@ -32,7 +32,8 @@ Some deleted repositories can be restored within 90 days of deletion. {% ifversi
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
1. In the "Danger Zone" section, click **Delete this repository**.
|
||||
1. **Read the warnings**.
|
||||
1. Scroll down to the "Danger Zone" section and click **Delete this repository**.
|
||||
1. Click **I want to delete this repository**.
|
||||
1. Read the warnings and click **I have read and understand these effects**.
|
||||
1. To verify that you're deleting the correct repository, in the text box, type the name of the repository you want to delete.
|
||||
1. Click **I understand the consequences, delete this repository**.
|
||||
1. Click **Delete this repository**.
|
||||
|
||||
@@ -107,7 +107,7 @@ If you want to mirror a repository in another location, including getting update
|
||||
git remote set-url --push origin https://{% data variables.command_line.codeblock %}/EXAMPLE-USER/MIRRORED
|
||||
```
|
||||
|
||||
As with a bare clone, a mirrored clone includes all remote branches and tags, but all local references will be overwritten each time you fetch, so it will always be the same as the original repository. Setting the URL for pushes simplifies pushing to your mirror.
|
||||
As with a bare clone, a mirrored clone includes all remote branches and tags, but all local references will be overwritten each time you fetch, so it will always be the same as the original repository. Setting the URL for pushes simplifies pushing to your mirror.
|
||||
|
||||
1. To update your mirror, fetch updates and push.
|
||||
|
||||
|
||||
@@ -17,9 +17,14 @@ topics:
|
||||
- Repositories
|
||||
shortTitle: Repository visibility
|
||||
---
|
||||
|
||||
## About repository visibility changes
|
||||
|
||||
Organization owners can restrict the ability to change repository visibility to organization owners only. For more information, see "[AUTOTITLE](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)."
|
||||
{% note %}
|
||||
|
||||
**Note:** If you can't change a repository's visibility, the organization owner may have restricted the ability to change repository visibility to organization owners only. For more information, see "[AUTOTITLE](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
@@ -51,7 +56,7 @@ We recommend reviewing the following caveats before you change the visibility of
|
||||
- If you change a repository's visibility from internal to private, {% data variables.product.prodname_dotcom %} will remove forks that belong to any user without access to the newly private repository. {% ifversion fpt or ghes or ghec %}The visibility of any forks will also change to private.{% elsif ghae %}If the internal repository has any forks, the visibility of the forks is already private.{% endif %} For more information, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)"
|
||||
{%- endif %}
|
||||
{%- ifversion fpt %}
|
||||
- If you're using {% data variables.product.prodname_free_user %} for personal accounts or organizations, some features won't be available in the repository after you change the visibility to private. Any published {% data variables.product.prodname_pages %} site will be automatically unpublished. If you added a custom domain to the {% data variables.product.prodname_pages %} site, you should remove or update your DNS records before making the repository private, to avoid the risk of a domain takeover. For more information, see "[AUTOTITLE](/get-started/learning-about-github/githubs-plans) and "[AUTOTITLE](/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site)."
|
||||
- If you're using {% data variables.product.prodname_free_user %} for personal accounts or organizations, some features won't be available in the repository after you change the visibility to private. Any published {% data variables.product.prodname_pages %} site will be automatically unpublished. If you added a custom domain to the {% data variables.product.prodname_pages %} site, you should remove or update your DNS records before making the repository private, to avoid the risk of a domain takeover. For more information, see "[AUTOTITLE](/get-started/learning-about-github/githubs-plans)" and "[AUTOTITLE](/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site)."
|
||||
{%- endif %}
|
||||
{%- ifversion fpt or ghec %}
|
||||
- {% data variables.product.prodname_dotcom %} will no longer include the repository in the {% data variables.product.prodname_archive %}. For more information, see "[AUTOTITLE](/repositories/archiving-a-github-repository/about-archiving-content-and-data-on-github#about-the-github-archive-program)."
|
||||
|
||||
Reference in New Issue
Block a user