Merge pull request github#36397 from github/repo-sync

Repo sync
MelnikovAG · Feb 20, 2025 · de10c43 · de10c43
2 parents 1f94d09 + ead57d1
commit de10c43
Show file tree

Hide file tree

Showing 4 changed files with 16 additions and 3 deletions.
diff --git a/.../choosing-what-your-workflow-does/caching-dependencies-to-speed-up-workflows.md b/.../choosing-what-your-workflow-does/caching-dependencies-to-speed-up-workflows.md
@@ -58,6 +58,19 @@ When a cache is created by a workflow run triggered on a pull request, the cache
 
 Multiple workflow runs in a repository can share caches. A cache created for a branch in a workflow run can be accessed and restored from another workflow run for the same repository and branch.
 
+{% ifversion ghes %}
+
+> [!NOTE]
+> As objects are retrieved from or put into the cache directly from runners, Actions runners must have direct connectivity to the Actions object storage configured in {% data variables.product.prodname_ghe_server %}, such as AWS S3 or Azure Blob Storage. Self-hosted runners authenticate with the blob storage provider using an access URL provided by the {% data variables.product.prodname_ghe_server %} instance. This URL supplies the blob storage provider with valid temporary authentication credentials. This process is initiated by the instance itself, which mediates all requests to the object storage.
+>
+> This means that `actions/cache` requires a HTTPS connection to the blob storage in order to work correctly.
+>
+> All the metadata are managed by the artifact cache service, which is a microservice within {% data variables.product.prodname_actions %}.
+>
+> For more information on cache storage, see [External storage requirements](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#external-storage-requirements).
+
+{% endif %}
+
 ## Using the `cache` action
 
 The [`cache` action](https://github.com/actions/cache) will attempt to restore a cache based on the `key` you provide. When the action finds a cache that _exactly_ matches the key, the action restores the cached files to the `path` you configure.

diff --git a/...t/configure-personal-settings/configuring-github-copilot-in-your-environment.md b/...t/configure-personal-settings/configuring-github-copilot-in-your-environment.md
@@ -269,7 +269,7 @@ To configure {% data variables.product.prodname_copilot %} in {% data variables.
 
 You can use the default keyboard shortcuts for {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_copilot %}. Search keyboard shortcuts by command name in the Keyboard Shortcuts editor.
 
-Alternatively, you can rebind the shortcut for each command in the Keyboard Shortcuts editor. For more information, see the [VS Code documentation on key bindings](https://code.visualstudio.com/docs/getstarted/keybindings).
+Alternatively, you can rebind the shortcut for each command in the Keyboard Shortcuts editor. For more information, see the [VS Code documentation on editing shortcuts](https://code.visualstudio.com/Docs/editor/keybindings).
 
 ### Keyboard shortcuts for macOS
 

diff --git a/...loud/migrating-repositories-from-bitbucket-server-to-github-enterprise-cloud.md b/...loud/migrating-repositories-from-bitbucket-server-to-github-enterprise-cloud.md
@@ -229,7 +229,7 @@ gh bbs2gh migrate-repo --archive-path ARCHIVE-PATH \
 {% data reusables.enterprise-migration-tool.abort-migration %}
 
 ```shell copy
-gh bb2gh abort-migration --migration-id MIGRATION-ID
+gh bbs2gh abort-migration --migration-id MIGRATION-ID
 ```
 
 ## Step 6: Validate your migration and check the error log

diff --git a/data/features/custom-properties-on-create.yml b/data/features/custom-properties-on-create.yml
@@ -2,4 +2,4 @@
 # Allows actors with the ability to create repos to be required to enter custom properties on repo creation.
 versions:
   ghec: '*'
-  ghes: '>= 3.15'
+  ghes: '>= 3.16'