Merge branch 'main' into patch-1

Author: putku45

.github/agents/readability-editor.md

@@ -36,6 +36,7 @@ You are an expert editor for the GitHub Docs content team. Your job is to maximi
 - When two possible phrasings are equally clear, choose the one with fewer words. Brevity directly improves readability.
 - Use full terms and not their shortened versions.
 - Use active voice and personal pronouns ("you," "your"); favor present tense.
+- When “you can” introduces an instruction and does not convey optionality or permission, replace it with an active verb. For example, “You can enable” becomes “Enable”. Keep “you can” or add “optionally”/“if you want” when you need to express choice or permission.
 - Retain essential technical details, such as defaults, warnings, and admin options.
 - Do not alter the intent of verbs and actions (ex. "navigate" does not necessarily mean "select").
 - Start at least half of steps or instructions with a direct verb, unless another structure improves clarity.

.github/workflows/feedback-prompt.yml

@@ -53,22 +53,21 @@ jobs:
               .join(" ");
 
             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.";
+                " - Thanks for your contribution! " +
+                "If you think something could be improved about the contributor experience, please post in `#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.";
+                " - Thanks for your contribution! " +
+                "If you think something could be improved about the contributor experience, please post in `#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.";
+                "👋 Thanks for your contribution! " +
+                "If you think something could be improved about the contributor experience, please post in `#docs-contributor-feedback` on Slack.";
             }
 
             await github.rest.issues.createComment({

.github/workflows/index-general-search.yml

@@ -152,7 +152,7 @@ jobs:
 
           # first sleep to give it a chance to start
           sleep 6
-          curl --retry-connrefused --retry 4 -I http://localhost:4002/
+          curl --retry-connrefused --retry 6 -I http://localhost:4002/
 
       - if: ${{ failure() }}
         name: Debug server outputs on errors
@@ -232,7 +232,7 @@ jobs:
 
       - name: Upload failures artifact
         if: ${{ steps.check-failures.outputs.has_failures == 'true' }}
-        uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # v4.6.2
+        uses: actions/upload-artifact@b7c566a772e6b6bfb58ed0dc250532a479d7789f # v6.0.0
         with:
           name: search-failures-${{ matrix.language }}
           path: /tmp/records/failures-summary.json
@@ -254,7 +254,7 @@ jobs:
         uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
 
       - name: Download all failure artifacts
-        uses: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093 # v4.3.0
+        uses: actions/download-artifact@37930b1c2abaa49bbe596cd826c3c89aef350131 # v7.0.0
         with:
           pattern: search-failures-*
           path: /tmp/failures

README.md

@@ -1,6 +1,7 @@
 # GitHub Docs <!-- omit in toc -->
 
-Welcome to GitHub Docs! GitHub’s documentation is open source, meaning anyone from inside or outside the company can contribute. For full contributing guidelines, visit our [contributing guide](https://docs.github.com/en/contributing)
+Welcome to GitHub Docs! GitHub’s documentation is open source, meaning anyone from inside or outside the company can contribute. For full contributing guidelines, visit our [contributing guide](https://docs.github.com/en/contributing).
+
 
 ## Quick links by contributor type
 

assets/images/help/copilot/copilot-cli-welcome.png

@@ -27,7 +27,7 @@ Runner groups are used to control which repositories can run jobs on your {% dat
 * **Runners at the enterprise level:** {% data reusables.actions.about-enterprise-level-runner-groups %}
 * **Runners at the organization level:** {% data reusables.actions.about-organization-level-runner-groups %}
 
-For example, the following diagram has a runner group named `grp-ubuntu-20.04-16core` at the enterprise level. Before the repository named `octo-repo` can use the runners in the group, you must first configure the group at the enterprise level to allow access to the `octo-org` organization. You must then configure the group at the organization level to allow access to `octo-repo`.
+For example, the following diagram has a runner group named `grp-ubuntu-24.04-16core` at the enterprise level. Before the repository named `octo-repo` can use the runners in the group, you must first configure the group at the enterprise level to allow access to the `octo-org` organization. You must then configure the group at the organization level to allow access to `octo-repo`.
 
 ![Diagram showing a runner group defined at the enterprise level with an organization configuration that allows access for two repositories.](/assets/images/help/actions/hosted-runner-mgmt.png)
 

content/actions/how-tos/manage-runners/larger-runners/control-access.md

@@ -85,15 +85,15 @@ Use the labels in the table below to run your workflows on the corresponding mac
 
 {% data reusables.actions.runner-labels-implicit %}
 
-In this example, the `runs-on` key sends the job to any available runner that has been assigned the `ubuntu-20.04-16core` label:
+In this example, the `runs-on` key sends the job to any available runner that has been assigned the `ubuntu-24.04-16core` label:
 
 ```yaml
 name: learn-github-actions
 on: [push]
 jobs:
   check-bats-version:
     runs-on:
-      labels: ubuntu-20.04-16core
+      labels: ubuntu-24.04-16core
     steps:
       - uses: {% data reusables.actions.action-checkout %}
       - uses: {% data reusables.actions.action-setup-node %}
@@ -148,7 +148,7 @@ name: learn-github-actions-testing
 on: [push]
 jobs:
   build:
-    runs-on: macos-13-xlarge
+    runs-on: macos-26-xlarge
     steps:
       - uses: {% data reusables.actions.action-checkout %}
       - name: Build

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

@@ -50,6 +50,9 @@ Single-CPU {% data variables.product.github %}-hosted runners are available in b
 
 `ubuntu-slim` runners execute Actions workflows in Ubuntu Linux, inside a container rather than a full VM instance. When the job begins, {% data variables.product.github %} automatically provisions a new container for that job. All steps in the job execute in the container, allowing the steps in that job to share information using the runner's file system. When the job has finished, the container is automatically decommissioned. Each container provides hypervisor level 2 isolation.
 
+> [!NOTE]
+> The container for `ubuntu-slim` runners runs in unprivileged mode. This means that some operations requiring elevated privileges—such as mounting file systems, using Docker-in-Docker, or accessing low-level kernel features—are not supported.
+
 A minimal set of tools is installed on the `ubuntu-slim` runner image, appropriate for lightweight tasks. For details on what software is installed on the `ubuntu-slim` image, see the [README file](https://github.com/actions/runner-images/blob/main/images/ubuntu-slim/ubuntu-slim-Readme.md) in the `actions/runner-images` repository.
 
 #### Usage limits

content/actions/reference/runners/github-hosted-runners.md

@@ -953,7 +953,7 @@ jobs:
   example_matrix:
     strategy:
       matrix:
-        os: [ubuntu-22.04, ubuntu-20.04]
+        os: [ubuntu-22.04, ubuntu-24.04]
         version: [10, 12, 14]
     runs-on: {% raw %}${{ matrix.os }}{% endraw %}
     steps:

content/actions/reference/workflows-and-actions/workflow-syntax.md

@@ -22,9 +22,7 @@ You can configure the web UI for your enterprise to display a custom footer with
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
-1. Under **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**, click **Profile**.
-1. At the top of the page, under the navigation bar, click **Custom footer**.
-
-   ![Screenshot of the "Profile" page for an enterprise account. A tab, labeled "Custom footer", is outlined in dark orange.](/assets/images/enterprise/custom-footer/custom-footer-section.png)
+1. Under **{% octicon "gear" aria-hidden="true" aria-label="gear" %} Settings**, click **General**.
+1. Navigate to **Custom footer**.
 1. Under each "Footer Link" heading, type a title and URL.
-1. To save the content and display the custom footer, click **Update custom footer**.
+1. To save the content and display the custom footer, click **Update footer**.