Merge branch 'main' into mark-mxwl-patch-1

.github/branch_protection_settings/main.json

@@ -38,7 +38,8 @@
       "fixtures",
       "frame",
       "products",
-      "workflows"
+      "workflows",
+      "lint-code"
     ],
     "contexts_url": "https://api.github.com/repos/github/docs-internal/branches/main/protection/required_status_checks/contexts",
     "checks": [
@@ -79,7 +80,8 @@
       { "context": "fixtures", "app_id": 15368 },
       { "context": "frame", "app_id": 15368 },
       { "context": "products", "app_id": 15368 },
-      { "context": "workflows", "app_id": 15368 }
+      { "context": "workflows", "app_id": 15368 },
+      { "context": "lint-code", "app_id": 15368 }
     ]
   },
   "restrictions": {

.github/workflows/link-check-on-pr.yml

@@ -43,6 +43,7 @@ jobs:
           SHOULD_COMMENT: ${{ secrets.DOCS_BOT_PAT_WRITEORG_PROJECT != '' }}
           CHECK_EXTERNAL_LINKS: false
           CREATE_REPORT: false
+          CHECK_ANCHORS: true
           # Not strictly necessary bit it makes warmServer() a bit faster
           # because it only bothers with English to begin with, which
           # we're filtering on anyway once the list of all pages has

content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-user-account-settings/managing-accessibility-settings.md

@@ -22,12 +22,6 @@ You can decide whether you want to use some or all keyboard shortcuts on {% ifve
 
 You can control whether links in text blocks on {% data variables.location.product_location %} are underlined and therefore more distinguishable.
 
-{% note %}
-
-**Note:** The option to show link underlines is currently in beta and subject to change.
-
-{% endnote %}
-
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.accessibility_settings %}
 1. Under "Content", manage settings for link appearance.

content/actions/automating-builds-and-tests/about-continuous-integration.md

@@ -16,7 +16,7 @@ topics:
   - CI
 shortTitle: Continuous integration
 ---
- 
+
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
 ## About continuous integration
@@ -41,11 +41,11 @@ In addition to helping you set up CI workflows for your project, you can use {%
 
 For a definition of common terms, see "[AUTOTITLE](/actions/learn-github-actions/understanding-github-actions)."
 
-## Starter workflow
+## Starter workflows
 
-{% data variables.product.product_name %} offers CI starter workflow for a variety of languages and frameworks.
+{% data variables.product.product_name %} offers CI starter workflows for a variety of languages and frameworks.
 
-Browse the complete list of CI starter workflow offered by {% data variables.product.company_short %} in the {% ifversion fpt or ghec %}[actions/starter-workflows](https://github.com/actions/starter-workflows/tree/main/ci) repository{% else %} `actions/starter-workflows` repository on {% data variables.location.product_location %}{% endif %}.
+Browse the complete list of CI starter workflows offered by {% data variables.product.company_short %} in the {% ifversion fpt or ghec %}[actions/starter-workflows](https://github.com/actions/starter-workflows/tree/main/ci) repository{% else %} `actions/starter-workflows` repository on {% data variables.location.product_location %}{% endif %}.
 
 {% ifversion fpt or ghec %}
 

content/actions/learn-github-actions/contexts.md

@@ -90,9 +90,7 @@ The following table indicates where each context and special function can be use
 
 | Workflow key | Context | Special functions |
 | ---- | ------- | ----------------- |
-{%- ifversion actions-run-name %}
 | <code>run-name</code> | <code>github, inputs, vars</code> | None |
-{%- endif %}
 | <code>concurrency</code> | <code>github, inputs, vars</code> | None |
 | <code>env</code> | <code>github, secrets, inputs, vars</code> | None |
 | <code>jobs.&lt;job_id&gt;.concurrency</code> | <code>github, needs, strategy, matrix, inputs, vars</code> | None |

content/actions/quickstart.md

@@ -13,26 +13,42 @@ topics:
   - Fundamentals
 shortTitle: Quickstart
 ---
- 
+
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
 ## Introduction
 
-You only need a {% data variables.product.prodname_dotcom %} repository to create and run a {% data variables.product.prodname_actions %} workflow. In this guide, you'll add a workflow that demonstrates some of the essential features of {% data variables.product.prodname_actions %}.
+{% data reusables.actions.about-actions %}  You can create workflows that run tests whenever you push a change to your repository, or that deploy merged pull requests to production.
+
+This quickstart guide shows you how to use the user interface of {% data variables.location.product_location %} to add a workflow that demonstrates some of the essential features of {% data variables.product.prodname_actions %}.
+
+For an overview of {% data variables.product.prodname_actions %} workflows, see "[AUTOTITLE](/actions/using-workflows/about-workflows)." If you want to learn about the various components that make up {% data variables.product.prodname_actions %}, see "[AUTOTITLE](/actions/learn-github-actions/understanding-github-actions)."
 
-The following example shows you how {% data variables.product.prodname_actions %} jobs can be automatically triggered, where they run, and how they can interact with the code in your repository.
+## Prerequisites
+
+This guide assumes that:
+- You have at least a basic knowledge of how to use {% data variables.product.prodname_dotcom %}. If you don't, you'll find it helpful to read some of the articles in the documentation for repositories and pull requests first. For example, see "[AUTOTITLE](/repositories/creating-and-managing-repositories/quickstart-for-repositories)," "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches)," and "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)."
+- You have a repository on {% data variables.location.product_location %} where you can add files.
+- You have access to {% data variables.product.prodname_actions %}.
+
+  > [!NOTE] If the {% octicon "play" aria-hidden="true" %} **Actions** tab is not displayed under the name of your repository on {% data variables.product.prodname_dotcom %}, it may be because Actions is disabled for the 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)."
 
 ## Creating your first workflow
 
-1. Create a `.github/workflows` directory in  your repository on {% data variables.product.prodname_dotcom %} if this directory does not already exist. The directory must have this exact name in order for {% data variables.product.prodname_dotcom %} to discover any {% data variables.product.prodname_actions %} workflows that it contains.
-1. In the `.github/workflows` directory, create a file with the `.yml` or `.yaml` extension. This tutorial will use `github-actions-demo.yml` as the file name. For more information, see "[AUTOTITLE](/repositories/working-with-files/managing-files/creating-new-files)."
+1. In your repository on {% data variables.location.product_location %}, create a workflow file called `github-actions-demo.yml` in the `.github/workflows` directory. To do this:
+   - If the `.github/workflows` directory already exists, navigate to that directory on {% data variables.product.prodname_dotcom %}, click **Add file**, then click **Create new file**, and name the file `github-actions-demo.yml`.
+   - If your repository doesn't have a `.github/workflows` directory, go to the main page of the repository on {% data variables.product.prodname_dotcom %}, click **Add file**, then click **Create new file**, and name the file `.github/workflows/github-actions-demo.yml`. This creates the `.github` and `workflows` directories and the `github-actions-demo.yml` file in a single step.
+
+   > [!NOTE]
+   > For {% data variables.product.prodname_dotcom %} to discover any {% data variables.product.prodname_actions %} workflows in your repository, you must save the workflow files in a directory called `.github/workflows`.
+   >
+   > You can give the workflow file any name you like, but you must use `.yml` or `.yaml` as the file name extension. YAML is a markup language that's commonly used for configuration files.
+
 1. Copy the following YAML contents into the `github-actions-demo.yml` file:
 
    ```yaml copy
    name: GitHub Actions Demo
-   {%- ifversion actions-run-name %}
    run-name: {% raw %}${{ github.actor }}{% endraw %} is testing out GitHub Actions 🚀
-   {%- endif %}
    on: [push]
    jobs:
      Explore-GitHub-Actions:
@@ -51,29 +67,37 @@ The following example shows you how {% data variables.product.prodname_actions %
          - run: echo "🍏 This job's status is {% raw %}${{ job.status }}{% endraw %}."
    ```
 
-1. Scroll to the bottom of the page and select **Create a new branch for this commit and start a pull request**. Then, to create a pull request, click **Propose new file**.
+   At this stage you don't need to understand the details of this workflow. For now, you can just copy and paste the contents into the file. After completing this quickstart guide, you can learn about the syntax of workflow files in "[AUTOTITLE](/actions/using-workflows/about-workflows#understanding-the-workflow-file)," and for an explanation of {% data variables.product.prodname_actions %} contexts, such as `{% raw %}${{ github.actor }}{% endraw %}` and `{% raw %}${{ github.event_name }}{% endraw %}`, see "[AUTOTITLE](/actions/learn-github-actions/contexts)."
+
+1. Click **Commit changes**.
+1. In the "Propose changes" dialog, select either the option to commit to the default branch or the option to create a new branch and start a pull request. Then click **Commit changes** or **Propose changes**.
 
-   ![Screenshot of the "Commit new file" area of the page.](/assets/images/help/repository/actions-quickstart-commit-new-file.png)
+   ![Screenshot of the "Propose changes" dialog with the areas mentioned highlighted with an orange outline.](/assets/images/help/repository/actions-quickstart-commit-new-file.png)
 
 Committing the workflow file to a branch in your repository triggers the `push` event and runs your workflow.
 
+If you chose to start a pull request, you can continue and create the pull request, but this is not necessary for the purposes of this quickstart because the commit has still been made to a branch and will trigger the new workflow.
+
 ## Viewing your workflow results
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
 1. In the left sidebar, click the workflow you want to display, in this example "GitHub Actions Demo."
 
    ![Screenshot of the "Actions" page. The name of the example workflow, "GitHub Actions Demo", is highlighted by a dark orange outline.](/assets/images/help/repository/actions-quickstart-workflow-sidebar.png)
+
 1. From the list of workflow runs, click the name of the run you want to see, in this example "USERNAME is testing out GitHub Actions."
 1. In the left sidebar of the workflow run page, under **Jobs**, click the **Explore-GitHub-Actions** job.
 
    ![Screenshot of the "Workflow run" page. In the left sidebar, the "Explore-GitHub-Actions" job is highlighted with a dark orange outline.](/assets/images/help/repository/actions-quickstart-job.png)
+
 1. The log shows you how each of the steps was processed. Expand any of the steps to view its details.
 
    ![Screenshot of steps run by the workflow.](/assets/images/help/repository/actions-quickstart-logs.png)
 
    For example, you can see the list of files in your repository:
-   ![Screenshot of the "List files in the repository" step expanded to show the log output. The output for the step is highlighted with a dark orange highlight.](/assets/images/help/repository/actions-quickstart-log-detail.png)
+
+   ![Screenshot of the "List files in the repository" step expanded to show the log output. The output for the step is highlighted with an orange outline.](/assets/images/help/repository/actions-quickstart-log-detail.png)
 
 The example workflow you just added is triggered each time code is pushed to the branch, and shows you how {% data variables.product.prodname_actions %} can work with the contents of your repository. For an in-depth tutorial, see "[AUTOTITLE](/actions/learn-github-actions/understanding-github-actions)."
 

content/actions/using-workflows/workflow-syntax-for-github-actions.md

@@ -26,8 +26,6 @@ You must store workflow files in the `.github/workflows` directory of your repos
 
 {% data reusables.actions.workflows.workflow-syntax-name %}
 
-{% ifversion actions-run-name %}
-
 ## `run-name`
 
 The name for workflow runs generated from the workflow. {% data variables.product.prodname_dotcom %} displays the workflow run name in the list of workflow runs on your repository's "Actions" tab. If `run-name` is omitted or is only whitespace, then the run name is set to event-specific information for the workflow run. For example, for a workflow triggered by a `push` or `pull_request` event, it is set as the commit message or the title of the pull request.
@@ -43,7 +41,6 @@ run-name: Deploy to ${{ inputs.deploy_target }} by @${{ github.actor }}
 ```
 
 {% endraw %}
-{% endif %}
 
 ## `on`
 

content/admin/administering-your-instance/administering-your-instance-from-the-command-line/command-line-utilities.md

@@ -906,7 +906,7 @@ ghe-btop [ <port number> | --help | --usage ]
 
 #### ghe-governor
 
-This utility helps to analyze Git traffic. It queries _Governor_ data files, located under `/data/user/gitmon`. {% data variables.product.company_short %} holds one hour of data per file, retained for two weeks. For more information, see [Analyzing Git traffic using Governor](https://github.community/t/analyzing-git-traffic-using-governor/13516) in {% data variables.product.prodname_github_community %}.
+This utility helps to analyze Git traffic. It queries _Governor_ data files, located under `/data/user/gitmon`. {% data variables.product.company_short %} holds one hour of data per file, retained for two weeks. For more information, see [Analyzing Git traffic using Governor](https://github.com/orgs/community/discussions/34220) in {% data variables.product.prodname_github_community %}.
 
 ```bash
 ghe-governor <subcommand> <column> [options]

content/admin/administering-your-instance/administering-your-instance-from-the-web-ui/about-the-management-console.md

@@ -36,7 +36,8 @@ In the {% data variables.enterprise.management_console %}, you can perform admin
 
 - **Initial setup**: Walk through the initial setup process when first launching {% data variables.location.product_location %} by visiting {% data variables.location.product_location %}'s IP address in your browser.
 {%- ifversion enterprise-management-console-multi-user-auth %}
-- **Identity and access management**: Improve the security of {% data variables.location.product_location %} by creating dedicated user accounts for the {% data variables.enterprise.management_console %}. The root site administrator account can control these user accounts' access by assigning either the editor or operator role. For more information, see "[AUTOTITLE](/admin/configuration/administering-your-instance-from-the-management-console/managing-access-to-the-management-console)."
+- **Identity and access management**: Improve the security of {% data variables.location.product_location %} by creating dedicated user accounts for the {% data variables.enterprise.management_console %}. {% ifversion management-console-editor %}The root site administrator account can control these user accounts' access by assigning either the editor or operator role. {% endif %}For more information, see "[AUTOTITLE](/admin/configuration/administering-your-instance-from-the-management-console/managing-access-to-the-management-console)."{% ifversion management-console-editor %}
+  {% data reusables.enterprise.editor-role-note %}{% endif %}
 {%- endif %}
 - **Configuring authentication policies for the {% data variables.enterprise.management_console %}**: Set rate limits for login attempts, and the lockout duration if someone exceeds the rate limit. For more information, see "[AUTOTITLE](/admin/configuration/administering-your-instance-from-the-management-console/managing-access-to-the-management-console#configuring-rate-limits-for-authentication-to-the-management-console)."
 - **Configuring basic settings for your instance**: Configure DNS, hostname, SSL, user authentication, email, monitoring services, and log forwarding on the Settings page.

content/admin/administering-your-instance/administering-your-instance-from-the-web-ui/managing-access-to-the-management-console.md

@@ -24,7 +24,7 @@ topics:
 
 There are two types of user accounts for the {% data variables.enterprise.management_console %} on a {% data variables.product.product_name %} instance. The root site administrator account authenticates with a password established during the initial setup of {% data variables.location.product_location %}.
 
-The root site administrator can create additional accounts, and assign one of two roles to each.
+The root site administrator can create additional accounts{% ifversion management-console-editor %}, and assign one of two roles to each{% endif %}.
 
 ### Root site administrator
 
@@ -36,12 +36,19 @@ Only the root site administrator can create and delete {% data variables.enterpr
 
 {% data variables.enterprise.management_console %} users can perform most administrative tasks for {% data variables.location.product_location %}. For heightened security, {% data variables.enterprise.management_console %} users cannot create or delete {% data variables.enterprise.management_console %} user accounts.
 
+{% ifversion management-console-editor %}
+
 Only {% data variables.enterprise.management_console %} users with the operator role can manage SSH keys.
 
+{% data reusables.enterprise.editor-role-note %}
+
 The root site administrator can provision one of two roles for {% data variables.enterprise.management_console %} users:
 
 - **Editor**: A {% data variables.enterprise.management_console %} user with the editor role can perform basic administrative tasks for {% data variables.location.product_location %} in the {% data variables.enterprise.management_console %}. Editors cannot add public SSH keys to the {% data variables.enterprise.management_console %} to grant administrative SSH access to the instance.
-- **Operator**: A {% data variables.enterprise.management_console %} user with the operator role can perform basic administrative tasks for {% data variables.location.product_location %} in the {% data variables.enterprise.management_console %}. Users with the operator role can add SSH keys to the {% data variables.enterprise.management_console %} to grant administrative access to the instance via SSH.
+- **Operator**: A {% data variables.enterprise.management_console %} user with the operator role
+{%- else %}
+{% data variables.enterprise.management_console %} users, sometimes called operators,
+{%- endif %} can perform basic administrative tasks for {% data variables.location.product_location %} in the {% data variables.enterprise.management_console %} and can add SSH keys to the {% data variables.enterprise.management_console %} to grant administrative access to the instance via SSH.
 
 ## Creating or deleting a user account for the {% data variables.enterprise.management_console %}
 
@@ -50,7 +57,7 @@ While signed into the {% data variables.enterprise.management_console %} as the
 {% data reusables.enterprise_site_admin_settings.click-user-management %}
 1. Click **Create user**.
 1. Fill in the user's name, username, and email address.
-1. Use the drop-down menu to select the user's role. You may select the editor or operator role.
+{% ifversion management-console-editor %}1. Use the drop-down menu to select the user's role. You may select the editor or operator role.{% endif %}
 1. To finish creating the user account, click **Create**. If email notifications are configured for the instance, the user will automatically receive an invitation email with access instructions for the {% data variables.enterprise.management_console %}. For more information, see "[Inviting new {% data variables.enterprise.management_console %} users](#inviting-new-management-console-users)."
 1. Optionally, to delete a {% data variables.enterprise.management_console %} user account, click {% octicon "trash" aria-label="The trash symbol" %} to the right of any user account you wish to delete. Then confirm deletion.