Merge pull request #34859 from github/repo-sync

Repo sync

content/get-started/writing-on-github/working-with-advanced-formatting/organizing-information-with-collapsed-sections.md

@@ -47,6 +47,7 @@ Optionally, to make the section display as open by default, add the `open` attri
 
 ```html
 <details open>
+```
 
 ## Further reading
 

content/migrations/using-github-enterprise-importer/migrating-between-github-products/migrating-repositories-from-github-enterprise-server-to-github-enterprise-cloud.md

@@ -486,6 +486,8 @@ gh gei migrate-repo --github-source-org SOURCE --source-repo CURRENT-NAME --gith
 
 {% data reusables.enterprise-migration-tool.skip-releases %}
 
+{% data reusables.enterprise-migration-tool.set-repository-visibility %}
+
 {% data reusables.enterprise-migration-tool.migrate-repo-table-ec %}
 {% data reusables.enterprise-migration-tool.ghes-api-url-placeholder %}
 {% data reusables.enterprise-migration-tool.azure-storage-connection-string-placeholder %}

data/reusables/copilot/sku-isolation.md

@@ -1,4 +1,4 @@
-> [!NOTE] {% data variables.product.prodname_copilot_sku_isolation %} is currently in {% data variables.release-phases.public_preview %} and subject to change. <!-- expires 2024-10-31 -->This feature will be enabled for all users on October 31, 2024.<!-- end expires 2024-10-31 -->
+> [!NOTE] {% data variables.product.prodname_copilot_sku_isolation %} is currently in {% data variables.release-phases.public_preview %} and subject to change. <!-- expires 2024-11-04 -->This feature will be enabled for all users on November 4, 2024.<!-- end expires 2024-11-04 -->
 
 ## About {% data variables.product.prodname_copilot_sku_isolation %}
 
@@ -11,21 +11,21 @@ Configuring {% data variables.product.prodname_copilot_sku_isolation %} will aff
 * {% data variables.product.prodname_mobile %} Apps
 * {% data variables.product.prodname_copilot_cli_short %}
 
-<!-- expires 2024-10-31 -->
-On October 31, 2024, we will enable {% data variables.product.prodname_copilot_sku_isolation %} for all users. This will ensure that users are accessing {% data variables.product.prodname_copilot %} through an endpoint that is specific to their {% data variables.product.prodname_copilot_short %} subscription. Only {% data variables.product.prodname_copilot_business_short %} users will be able to connect to the {% data variables.product.prodname_copilot_business_short %} endpoint and only {% data variables.product.prodname_copilot_enterprise_short %} users will be able to connect to the {% data variables.product.prodname_copilot_enterprise_short %} endpoint.
+<!-- expires 2024-11-04 -->
+On November 4, 2024, we will enable {% data variables.product.prodname_copilot_sku_isolation %} for all users. This will ensure that users are accessing {% data variables.product.prodname_copilot %} through an endpoint that is specific to their {% data variables.product.prodname_copilot_short %} subscription. Only {% data variables.product.prodname_copilot_business_short %} users will be able to connect to the {% data variables.product.prodname_copilot_business_short %} endpoint and only {% data variables.product.prodname_copilot_enterprise_short %} users will be able to connect to the {% data variables.product.prodname_copilot_enterprise_short %} endpoint.
 
-Optionally, if you are a customer with a {% data variables.product.prodname_dotcom %} account representative and you want to block access to {% data variables.product.prodname_copilot_individuals_short %} on your network before October 31, ask your representative about enabling {% data variables.product.prodname_copilot_sku_isolation %} ahead of this date.
+Optionally, if you are a customer with a {% data variables.product.prodname_dotcom %} account representative and you want to block access to {% data variables.product.prodname_copilot_individuals_short %} on your network before November 4, ask your representative about enabling {% data variables.product.prodname_copilot_sku_isolation %} ahead of this date.
 
 ## Important steps to ensure continued access to {% data variables.product.prodname_copilot %}
 
-Between now and October 31, you should ensure that your firewall allows access to all of the hostnames listed in "[AUTOTITLE](/copilot/managing-copilot/managing-github-copilot-in-your-organization/configuring-your-proxy-server-or-firewall-for-copilot)."
-<!-- end expires 2024-10-31 -->
+Between now and November 4, you should ensure that your firewall allows access to all of the hostnames listed in "[AUTOTITLE](/copilot/managing-copilot/managing-github-copilot-in-your-organization/configuring-your-proxy-server-or-firewall-for-copilot)."
+<!-- end expires 2024-11-04 -->
 
 ## Configuring {% data variables.product.prodname_copilot_sku_isolation %} for your enterprise
 
-<!-- expires 2024-10-31 -->
-Before October 31, 2024, you should perform the following steps to ensure users can continue to access {% data variables.product.prodname_copilot %}.
-<!-- end expires 2024-10-31 -->
+<!-- expires 2024-11-04 -->
+Before November 4, 2024, you should perform the following steps to ensure users can continue to access {% data variables.product.prodname_copilot %}.
+<!-- end expires 2024-11-04 -->
 
 1. Ensure your members have updated to at least the minimum version of their {% data variables.product.prodname_copilot_short %} client listed below.
     * For {% data variables.product.prodname_vscode %}, use Copilot Chat version 0.17 or later.

data/reusables/enterprise-migration-tool/review-migration-script.md

@@ -2,3 +2,4 @@ After you generate the script, review the file and, optionally, edit the script.
 
 * If there are any repositories you don't want to migrate, delete or comment out the corresponding lines.
 * If you want any repositories to have a different name in the destination organization, update the value for the corresponding `--target-repo` flag.
+* If you want to change the visibility of new repository, update the value for the corresponding `--target-repo-visibility` flag. By default, the script sets the same visibility as the source repository.

data/reusables/enterprise-migration-tool/set-repository-visibility.md

@@ -0,0 +1 @@
+Repositories are migrated with private visibility by default. To set the visibility, you can add the `--target-repo-visibility` flag, specifying `private`, `public`, or `internal`. If you're migrating to an {% data variables.enterprise.prodname_emu_enterprise %}, public repositories are not available.

data/reusables/enterprise-migration-tool/setting-repository-visibility.md

@@ -1,4 +1,5 @@
-All repositories are migrated as private, and only the user that ran the migration and organization owners will have access to the repository. If you don't want the repository to be private, change the visibility.
+All repositories are migrated as private by default, and only the user that ran the migration and organization owners will have access to the repository. If you don't want the repository to be private, change the visibility.
 
+* You can set a repository's visibility with the `--target-repo-visibility` CLI option or the `targetRepoVisibility` GraphQL property.
 * You can change a repository's visibility in the browser. For more information, see "[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility)."
 * Alternatively, you can use {% data variables.product.prodname_cli %} to change repository visibility from the command line. You can even add this command to the script that was generated to run your migrations. For more information, see [`gh repo edit`](https://cli.github.com/manual/gh_repo_edit) in the {% data variables.product.prodname_cli %} documentation.

data/reusables/enterprise-migration-tool/target-repository-visibility-placeholder.md

@@ -0,0 +1 @@
+TARGETREPOVISIBILITY | The visibility of the new repository. Must be `private`, `public`, or `internal`. If not set, your repository is migrated as private.