Merge branch 'main' into patch-1

Author: Sharra-writes

.github/workflows/feedback-prompt.yml

@@ -45,17 +45,32 @@ jobs:
         with:
           github-token: ${{ secrets.DOCS_BOT_PAT_BASE }}
           script: |
-            // Get PR author username
             const pr = context.payload.pull_request;
             const prAuthor = pr.user.login;
+            const assignees = (pr.assignees ?? [])
+              .filter(a => a.login.toLowerCase() !== "copilot")
+              .map(a => "@" + a.login)
+              .join(" ");
 
-            // Compose the comment body as a plain text message to post on the PR
-            const commentBody =
-              "👋 @" + prAuthor +
-              " - Please leave us feedback on your contributing experience! " +
-              "To do this, please go to `#docs-contributor-feedback` on Slack.";
+            let commentBody;
+
+            if (assignees) {
+              commentBody =
+                "👋 " + assignees +
+                " - Please leave us feedback on your contributing experience! " +
+                "To do this, please go to `#docs-contributor-feedback` on Slack.";
+            } else if (prAuthor.toLowerCase() !== "copilot") {
+              commentBody =
+                "👋 @" + prAuthor +
+                " - Please leave us feedback on your contributing experience! " +
+                "To do this, please go to `#docs-contributor-feedback` on Slack.";
+            } else {
+              // nobody to mention!
+              commentBody =
+                "👋 Please leave us feedback on your contributing experience! " +
+                "To do this, please go to `#docs-contributor-feedback` on Slack.";
+            }
 
-            // Post the comment
             await github.rest.issues.createComment({
               owner: context.repo.owner,
               repo: context.repo.repo,

CHANGELOG.md

@@ -1,5 +1,11 @@
 # Docs changelog
 
+**13 November 2025**
+
+We've published a new tutorial on [using custom instructions for Copilot code review](https://docs.github.com/copilot/tutorials/use-custom-instructions). In this tutorial you'll learn how to write effective custom instructions that help Copilot provide more relevant and actionable code reviews.
+
+<hr>
+
 **31 October 2025**
 
 A large amount of new information was added to the GitHub documentation website to coincide with the GitHub Universe 2025 conference. Here are links to some of the new and updated articles.

assets/images/help/copilot/activity-report-org.png

@@ -4,7 +4,7 @@ shortTitle: Use custom images
 intro: 'Create, manage, and use custom images for {% data variables.actions.github_hosted_larger_runners %} in your organization or enterprise.'
 versions:
   feature: actions-hosted-runners
-product: '{% data variables.actions.github_hosted_larger_runners %} are only available for organizations and enterprises using the {% data variables.product.prodname_team %} or {% data variables.product.prodname_ghe_cloud %} plans. <br><a href="https://github.com/pricing?ref_product=ghec&ref_type=trial&ref_style=button&utm_source=docs-signup-actions&utm_medium=docs&utm_campaign=universe25post" target="_blank" class="btn btn-primary mt-3 mr-3 no-underline"><span>Sign up for {% data variables.product.prodname_actions %}</span> {% octicon "link-external" height:16 %}</a>'
+product: '{% data variables.actions.github_hosted_larger_runners %} are only available for organizations and enterprises using the {% data variables.product.prodname_team %} or {% data variables.product.prodname_ghe_cloud %} plans. <br><a href="https://github.com/pricing?ref_product=ghec&ref_type=trial&ref_style=button" target="_blank" class="btn btn-primary mt-3 mr-3 no-underline"><span>Sign up for {% data variables.product.prodname_actions %}</span> {% octicon "link-external" height:16 %}</a>'
 
 ---
 

assets/images/help/copilot/byok-add-foundry.png

@@ -50,7 +50,7 @@ export no_proxy=example.com,localhost,127.0.0.1
 
 #### Windows
 
-On Windows, you can configure proxy settings either by setting environment variables or by using the [netsh command](https://learn.microsoft.com/en-us/windows/win32/winhttp/netsh-exe-commands&utm_source=docs-microsoft-proxy-servers&utm_medium=docs&utm_campaign=universe25post#set-advproxy).
+On Windows, you can configure proxy settings either by setting environment variables or by using the [netsh command](https://learn.microsoft.com/en-us/windows/win32/winhttp/netsh-exe-commands#set-advproxy).
 The netsh approach applies to applications and services that rely on the WinHTTP API.
 
 Setting environment variables is still required for runners that use private networking. Whether you also need to configure netsh depends on the applications used in your workflows.
@@ -88,8 +88,8 @@ If your runner is hosted in Azure, either as a self-hosted runner or a GitHub-ho
 You should add Azure metadata and management IPs to your `no_proxy` list to ensure the runner can access required Azure services. These endpoints allow Azure VMs to retrieve configuration and identity information needed for proper operation.
 
 The two Azure IPs are:
-* 168.63.129.16 (see [Azure IP address 168.63.129.16 overview](https://learn.microsoft.com/en-us/azure/virtual-network/what-is-ip-address-168-63-129-16?tabs=linux&utm_source=docs-microsoft-proxy-servers&utm_medium=docs&utm_campaign=universe25post))
-* 169.254.169.254 (see [Azure Instance Metadata Service](https://learn.microsoft.com/en-us/azure/virtual-machines/instance-metadata-service?tabs=linux&utm_source=docs-microsoft-proxy-servers&utm_medium=docs&utm_campaign=universe25post))
+* 168.63.129.16 (see [Azure IP address 168.63.129.16 overview](https://learn.microsoft.com/en-us/azure/virtual-network/what-is-ip-address-168-63-129-16?tabs=linux))
+* 169.254.169.254 (see [Azure Instance Metadata Service](https://learn.microsoft.com/en-us/azure/virtual-machines/instance-metadata-service?tabs=linux))
 
 ## Using a .env file to set the proxy configuration
 
@@ -109,4 +109,4 @@ no_proxy=example.com,myserver.local:443
 
 If you use Docker container actions or service containers in your workflows, you might also need to configure Docker to use your proxy server in addition to setting the above environment variables.
 
-For information on the required Docker configuration, see [Configure Docker to use a proxy server](https://docs.docker.com/network/proxy/?utm_source=docs-microsoft-proxy-servers&utm_medium=docs&utm_campaign=universe25post) in the Docker documentation.
+For information on the required Docker configuration, see [Configure Docker to use a proxy server](https://docs.docker.com/network/proxy/) in the Docker documentation.

assets/images/help/copilot/byok-add.png

@@ -61,13 +61,13 @@ These limits are subject to change.
 
 {% data variables.product.github %} Support **cannot** increase storage limits for {% data variables.product.prodname_actions %}.
 
-| {% data variables.product.github %} plan | Storage | Minutes (per month)|
-|------- | ------- | ---------|
-| {% data variables.product.prodname_free_user %} | 500 MB | 2,000 |
-| {% data variables.product.prodname_pro %} | 1 GB | 3,000 |
-| {% data variables.product.prodname_free_team %} for organizations | 500 MB | 2,000 |
-| {% data variables.product.prodname_team %} | 2 GB | 3,000 |
-| {% data variables.product.prodname_ghe_cloud %} | 50 GB | 50,000 |
+{% data reusables.billing.actions-included-quotas %}
+
+{% ifversion fpt or ghec %}
+
+For information about cache storage limits and how to increase them, see [Usage limits and eviction policy](/actions/reference/workflows-and-actions/dependency-caching#usage-limits-and-eviction-policy).
+
+{% endif %}
 
 ### Private IP scaling for vnet injection on larger runners
 

content/actions/how-tos/manage-runners/larger-runners/use-custom-images.md

@@ -17,6 +17,9 @@ versions:
   ghes: '*'
   ghec: '*'
 type: overview
+topics:
+  - Actions
+  - Workflows
 ---
 
 ## `cache` action usage
@@ -261,9 +264,25 @@ Multiple workflow runs in a repository can share caches. A cache created for a b
 
 ## Usage limits and eviction policy
 
-{% data variables.product.prodname_dotcom %} will remove any cache entries that have not been accessed in over 7 days. There is no limit on the number of caches you can store, but the total size of all caches in a repository is limited{% ifversion ghes %}. By default, the limit is 10 GB per repository, but this limit might be different depending on policies set by your enterprise owners or repository administrators.{% else %} to 10 GB.{% endif %} {% data reusables.actions.cache-eviction-policy %}
+{% data variables.product.prodname_dotcom %} applies limits to cache storage and retention to manage storage costs and prevent abuse. Understanding these limits helps you optimize your cache usage.
 
-{% data reusables.actions.cache-eviction-process %} The cache eviction process may cause cache thrashing, where caches are created and deleted at a high frequency. To reduce this, you can review the caches for a repository and take corrective steps, such as removing caching from specific workflows. See [AUTOTITLE](/actions/how-tos/managing-workflow-runs-and-deployments/managing-workflow-runs/manage-caches).{% ifversion ghes %} You can also increase the cache size limit for a repository. For more information, see [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-cache-storage-for-a-repository).
+### Default limits
+
+{% data variables.product.github %} will remove any cache entries that have not been accessed in over 7 days. There is no limit on the number of caches you can store, but the total size of all caches in a repository is limited. By default, the limit is 10 GB per repository, but this limit can be increased by enterprise owners, organization owners, or repository administrators. {% ifversion fpt or ghec %}Any usage beyond 10 GB is billed to your account.{% endif %} {% data reusables.actions.cache-eviction-policy %}
+
+{% data reusables.actions.cache-eviction-process %} The cache eviction process may cause cache thrashing, where caches are created and deleted at a high frequency. To reduce this, you can review the caches for a repository and take corrective steps, such as removing caching from specific workflows{% ifversion fpt or ghec %} or increasing your cache size. This functionality is only available to users with a payment method on file who opt in by configuring cache settings{% endif %}. See [AUTOTITLE](/actions/how-tos/managing-workflow-runs-and-deployments/managing-workflow-runs/manage-caches).{% ifversion ghes %} You can also increase the cache size limit for a repository. For more information, see [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-cache-storage-for-a-repository).
+
+{% endif %}
+{% ifversion fpt or ghec %}
+
+### Increasing cache size
+
+If you want to reduce the rate at which cache entries are evicted, you can increase the storage limits for your cache in the Actions Settings. Repositories owned by users can configure up to 10 TB per repository. For repositories owned by organizations, the maximum configurable limit is determined by the organization's settings. For organizations owned by an enterprise, the maximum configurable limit is determined by the enterprise's settings. Increasing the limit beyond the default 10 GB will incur additional costs, if that storage is used.
+
+For more information, see:
+* [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-cache-settings-for-your-repository)
+* [AUTOTITLE](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#managing-github-actions-cache-storage-for-your-organization)
+* [AUTOTITLE](/admin/enforcing-policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#artifact-and-log-retention)
 
 {% endif %}
 

content/actions/how-tos/manage-runners/use-proxy-servers.md

@@ -145,6 +145,28 @@ By default, artifacts and log files generated by workflows are retained for 90 d
 
 Changes only apply to new artifacts and log files.
 
+{% ifversion ghec %}
+
+### Cache settings
+
+You can configure maximum cache retention and size limits that will apply across your entire enterprise. If you increase the "Cache size eviction limit" beyond the 10 GB included in your plan, you will be charged for any additional storage of cached entries.
+
+By default:
+
+* Caches are retained for 7 days before automatic deletion.
+* The total cache storage limit is 10 GB per repository.
+
+You can customize these settings to set maximum limits for cache retention and cache storage size across your enterprise:
+
+* **Cache retention**: Configure up to 90 days for public repositories or 365 days for private and internal repositories.
+* **Cache size eviction limit**: Configure up to 10,000 GB per repository.
+
+The settings you configure at the enterprise level act as maximum limits. Organization owners can opt in to configure limits for their organization, but cannot exceed the limits set at the enterprise level. Repository administrators can opt in to configure limits for their repositories, but cannot exceed the limits set at the organization level.
+
+For more information about cache eviction, see [AUTOTITLE](/actions/reference/workflows-and-actions/dependency-caching#usage-limits-and-eviction-policy).
+
+{% endif %}
+
 {% ifversion ghes %}
 
 ### Maximum and default cache size limits