Merge pull request #53079 from github/repo-sync

Repo sync

contributing/debugging-the-docs-application.md

@@ -2,7 +2,7 @@
 
 This repo has configuration for debugging the codebase with VS Code's built-in Node Debugger.
 
-**Note**: These steps will only help with debugging issues in the Node.js codebase, not in the content files.
+**Note:** These steps will only help with debugging issues in the Node.js codebase, not in the content files.
 
 1. After running the build steps, start the app by running `npm run debug`.
 1. In VS Code, click on the Debugging icon in the Activity Bar to bring up the Debug view.

data/reusables/actions/actions-group-concurrency.md

@@ -2,14 +2,9 @@ This means that there can be at most one running and one pending job in a concur
 
 To also cancel any currently running job or workflow in the same concurrency group, specify `cancel-in-progress: true`.  To conditionally cancel currently running jobs or workflows in the same concurrency group, you can specify `cancel-in-progress` as an expression with any of the allowed expression contexts.
 
-{% note %}
-
-**Notes:**
-
-* The concurrency group name is case insensitive. For example, `prod` and `Prod` will be treated as the same concurrency group.
-* Ordering is not guaranteed for jobs or workflow runs using concurrency groups. Jobs or workflow runs in the same concurrency group are handled in an arbitrary order.
-
-{% endnote %}
+> [!NOTE]
+> * The concurrency group name is case insensitive. For example, `prod` and `Prod` will be treated as the same concurrency group.
+> * Ordering is not guaranteed for jobs or workflow runs using concurrency groups. Jobs or workflow runs in the same concurrency group are handled in an arbitrary order.
 
 ### Example: Using concurrency and the default behavior
 

data/reusables/actions/actions-importer-prerequisites.md

@@ -2,8 +2,5 @@
   * Docker is [installed](https://docs.docker.com/get-docker/) and running.
   * [{% data variables.product.prodname_dotcom %} CLI](https://cli.github.com) is installed.
 
-  {% note %}
-
-  **Note**: The {% data variables.product.prodname_actions_importer %} container and CLI do not need to be installed on the same server as your CI platform.
-
-  {% endnote %}
+  > [!NOTE]
+  > The {% data variables.product.prodname_actions_importer %} container and CLI do not need to be installed on the same server as your CI platform.

data/reusables/actions/actions-redirects-workflows.md

@@ -1,5 +1,2 @@
-{% note %}
-
-**Note:** To enhance security, {% data variables.product.prodname_actions %} does not support redirects for actions or reusable workflows. This means that when the owner, name of an action's repository, or name of an action is changed, any workflows using that action with the previous name will fail.
-
-{% endnote %}
+> [!NOTE]
+> To enhance security, {% data variables.product.prodname_actions %} does not support redirects for actions or reusable workflows. This means that when the owner, name of an action's repository, or name of an action is changed, any workflows using that action with the previous name will fail.

data/reusables/actions/actions-runner-controller-unsupported-customization.md

@@ -1,7 +1,4 @@
-{% warning %}
-
-**Warning:** This {% data variables.product.prodname_actions_runner_controller %} customization option may be outside the scope of what {% data variables.contact.github_support %} can assist with and may cause unexpected behavior when configured incorrectly.
-
-For more information about what {% data variables.contact.github_support %} can assist with, see [AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners-with-actions-runner-controller/about-support-for-actions-runner-controller).
-
-{% endwarning %}
+> [!WARNING]
+> This {% data variables.product.prodname_actions_runner_controller %} customization option may be outside the scope of what {% data variables.contact.github_support %} can assist with and may cause unexpected behavior when configured incorrectly.
+>
+> For more information about what {% data variables.contact.github_support %} can assist with, see [AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners-with-actions-runner-controller/about-support-for-actions-runner-controller).

data/reusables/actions/actions-secrets-variables-repository-access.md

@@ -1,10 +1,9 @@
 
 {% ifversion fpt %}
-{% note %}
 
-**Note:** Organization-level secrets and variables are not accessible by private repositories for {% data variables.product.prodname_free_user %}. For more information about upgrading your {% data variables.product.company_short %} subscription, see "[AUTOTITLE](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription)".
+> [!NOTE]
+> Organization-level secrets and variables are not accessible by private repositories for {% data variables.product.prodname_free_user %}. For more information about upgrading your {% data variables.product.company_short %} subscription, see "[AUTOTITLE](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription)".
 
-{% endnote %}
 {% endif %}
 
 When creating a secret or variable in an organization, you can use a policy to limit access by repository. For example, you can grant access to all repositories, or limit access to only private repositories or a specified list of repositories.

data/reusables/actions/actions-tab-new-runners-note.md

@@ -1,13 +1,7 @@
-{% note %}
-
-**Note:** Enterprise and organization owners{% ifversion custom-org-roles %} and users with the "Manage organization runners and runner groups" permission{% endif %} can create runners from this page. To create a new runner, click **New runner** at the top right of the list of runners to add runners to the repository.
-
-For more information, see {% ifversion actions-hosted-runners %}"[AUTOTITLE](/actions/using-github-hosted-runners/managing-larger-runners)" and {% endif %}"[AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/adding-self-hosted-runners)."
-
+> [!NOTE]
+> Enterprise and organization owners{% ifversion custom-org-roles %} and users with the "Manage organization runners and runner groups" permission{% endif %} can create runners from this page. To create a new runner, click **New runner** at the top right of the list of runners to add runners to the repository.
+>
+> For more information, see {% ifversion actions-hosted-runners %}"[AUTOTITLE](/actions/using-github-hosted-runners/managing-larger-runners)" and {% endif %}"[AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/adding-self-hosted-runners)."
 {% ifversion custom-org-roles %}
-
-For more information about custom organization roles, see "[AUTOTITLE](/organizations/managing-peoples-access-to-your-organization-with-roles/about-custom-organization-roles)."
-
+>For more information about custom organization roles, see "[AUTOTITLE](/organizations/managing-peoples-access-to-your-organization-with-roles/about-custom-organization-roles)."
 {% endif %}
-
-{% endnote %}

data/reusables/actions/allow-specific-actions-intro.md

@@ -21,11 +21,10 @@ When you choose {% data reusables.actions.policy-label-for-select-actions-workfl
   You can use the `*` wildcard character to match patterns. For example, to allow all actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %} in organizations that start with `space-org`, you can specify `space-org*/*`. To allow all actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %} in repositories that start with octocat, you can use `*/octocat**@*`. For more information about using the `*` wildcard, see "[AUTOTITLE](/actions/using-workflows/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet)."
 
   {% ifversion fpt or ghec %}
-  {% note %}
 
-  **Note:** For {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_free_team %} for organizations, or {% data variables.product.prodname_team %} plans, the **Allow specified actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %}** option is only available in public repositories.
+  > [!NOTE]
+  > For {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_free_team %} for organizations, or {% data variables.product.prodname_team %} plans, the **Allow specified actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %}** option is only available in public repositories.
 
-  {% endnote %}
   {% endif %}
 
 This procedure demonstrates how to add specific actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %} to the allow list.

data/reusables/actions/arc-runners-namespace.md

@@ -1,5 +1,2 @@
-{% note %}
-
-**Note:** Create the secret in the same namespace where the `gha-runner-scale-set` chart is installed. In this example, the namespace is `arc-runners` to match the quickstart documentation. For more information, see "[AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners-with-actions-runner-controller/quickstart-for-actions-runner-controller#configuring-a-runner-scale-set)."
-
-{% endnote %}
+> [!NOTE]
+> Create the secret in the same namespace where the `gha-runner-scale-set` chart is installed. In this example, the namespace is `arc-runners` to match the quickstart documentation. For more information, see "[AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners-with-actions-runner-controller/quickstart-for-actions-runner-controller#configuring-a-runner-scale-set)."

data/reusables/actions/azure-vnet-configure-azure-resources-script.md

@@ -4,16 +4,11 @@ Use the following script to set up a subnet for Azure private networking. The sc
 
 To use the script, fill in the placeholder environment variable values with the actual values and run the script from a bash shell or Windows Subsystem for Linux.
 
-{% note %}
-
-**Notes**:
-
-* Run the following script in the same directory where you saved the `actions-nsg-deployment.bicep` file.
-* When setting the `YOUR_AZURE_LOCATION` environment variable, use your region’s name. This value is different than your region’s display name. To see a list of names and display names, use `az account list-locations -o table`.
-* When you create the network settings resource, a service association link is applied to the subnet that you provide. This link prevents accidental deletion of the subnet while in use by the {% data variables.product.prodname_actions %} service.
-* If you customize this script to use network resources in existing subnets, you must ensure any existing network interfaces (NICs) connected to the subnet are deleted before the subnet is delegated to the {% data variables.product.prodname_actions %} service. Otherwise, the service will fail to apply the service association link to the subnet.
-
-{% endnote %}
+> [!NOTE]
+> * Run the following script in the same directory where you saved the `actions-nsg-deployment.bicep` file.
+> * When setting the `YOUR_AZURE_LOCATION` environment variable, use your region’s name. This value is different than your region’s display name. To see a list of names and display names, use `az account list-locations -o table`.
+> * When you create the network settings resource, a service association link is applied to the subnet that you provide. This link prevents accidental deletion of the subnet while in use by the {% data variables.product.prodname_actions %} service.
+> * If you customize this script to use network resources in existing subnets, you must ensure any existing network interfaces (NICs) connected to the subnet are deleted before the subnet is delegated to the {% data variables.product.prodname_actions %} service. Otherwise, the service will fail to apply the service association link to the subnet.
 
 ```bash copy
 #!/bin/bash

data/reusables/actions/azure-vnet-procedures-prereqs.md

@@ -14,11 +14,8 @@ You will use a script to automate configuring your Azure resources.
 
   If you use {% data variables.enterprise.data_residency %}, in the `AllowOutBoundGitHub` section, you must also include the egress IP ranges for {% data variables.enterprise.data_residency_site %}. See "[AUTOTITLE](/admin/data-residency/network-details-for-ghecom#ranges-for-egress-traffic)."
 
-  {% note %}
-
-  **Note:** As an alternative to using the following file, to allow {% data variables.product.prodname_actions %} to communicate with the runners, you can allow the same firewall domains that are required for communication between self-hosted runners and {% data variables.product.product_name %}. For more information, see "[AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/about-self-hosted-runners#communication-between-self-hosted-runners-and-github-enterprise-cloud)." To determine the appropriate subnet IP address range,  we recommend adding a 30% buffer to the maximum job concurrency you anticipate. For instance, if your network configuration's runners are set to a maximum job concurrency of 300, it's recommended to utilize a subnet IP address range that can accommodate at least 390 runners. This buffer helps ensure that your network can handle unexpected increases in VM needs to meet job concurrency without running out of IP addresses.
-
-  {% endnote %}
+  > [!NOTE]
+  > As an alternative to using the following file, to allow {% data variables.product.prodname_actions %} to communicate with the runners, you can allow the same firewall domains that are required for communication between self-hosted runners and {% data variables.product.product_name %}. For more information, see "[AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/about-self-hosted-runners#communication-between-self-hosted-runners-and-github-enterprise-cloud)." To determine the appropriate subnet IP address range,  we recommend adding a 30% buffer to the maximum job concurrency you anticipate. For instance, if your network configuration's runners are set to a maximum job concurrency of 300, it's recommended to utilize a subnet IP address range that can accommodate at least 390 runners. This buffer helps ensure that your network can handle unexpected increases in VM needs to meet job concurrency without running out of IP addresses.
 
   ```bicep copy
   @description('NSG for outbound rules')

data/reusables/actions/branch-and-tag-deployment-rules-configuration.md

@@ -1,5 +1,2 @@
-{% note %}
-
-**Note:** Name patterns must be configured for branches or tags individually.
-
-{% endnote %}
+> [!NOTE]
+> Name patterns must be configured for branches or tags individually.

data/reusables/actions/branch-requirement.md

@@ -1,5 +1,2 @@
-{% note %}
-
-**Note:** This event will only trigger a workflow run if the workflow file is on the default branch.
-
-{% endnote %}
+> [!NOTE]
+> This event will only trigger a workflow run if the workflow file is on the default branch.

data/reusables/actions/configuration-variables-beta-note.md

@@ -1,5 +1,2 @@
-{% note %}
-
-**Note:** Configuration variables for {% data variables.product.prodname_actions %} are in {% data variables.release-phases.public_preview %} and subject to change.
-
-{% endnote %}
+> [!NOTE]
+> Configuration variables for {% data variables.product.prodname_actions %} are in {% data variables.release-phases.public_preview %} and subject to change.

data/reusables/actions/context-example-note.md

@@ -1,5 +1,2 @@
-{% note %}
-
-**Note:** This context is an example only. The contents of a context depends on the workflow that you are running. {% data reusables.actions.context-contents %}
-
-{% endnote %}
+> [!NOTE]
+> This context is an example only. The contents of a context depends on the workflow that you are running. {% data reusables.actions.context-contents %}

data/reusables/actions/context-injection-warning.md

@@ -1,5 +1,2 @@
-{% warning %}
-
-**Warning:** When creating workflows and actions, you should always consider whether your code might execute untrusted input from possible attackers. Certain contexts should be treated as untrusted input, as an attacker could insert their own malicious content. For more information, see "[AUTOTITLE](/actions/security-guides/security-hardening-for-github-actions#understanding-the-risk-of-script-injections)."
-
-{% endwarning %}
+> [!WARNING]
+> When creating workflows and actions, you should always consider whether your code might execute untrusted input from possible attackers. Certain contexts should be treated as untrusted input, as an attacker could insert their own malicious content. For more information, see "[AUTOTITLE](/actions/security-guides/security-hardening-for-github-actions#understanding-the-risk-of-script-injections)."

data/reusables/actions/creating-a-runner-group-for-an-organization.md

@@ -7,11 +7,8 @@ Always include a security admonition above this procedure. This is either one of
 
 {% endcomment %}
 
-{% note %}
-
-**Note:** When creating a runner group, you must choose a policy that defines which repositories{% ifversion restrict-groups-to-workflows %} and workflows{% endif %} have access to the runner group. To change which repositories and workflows can access the runner group, organization owners{% ifversion custom-org-roles %} and users with the “Manage organization runners and runner groups” permission{% endif %} can set a policy for the organization. For more information, see "[AUTOTITLE](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#disabling-repository-level-self-hosted-runners)."
-
-{% endnote %}
+> [!NOTE]
+> When creating a runner group, you must choose a policy that defines which repositories{% ifversion restrict-groups-to-workflows %} and workflows{% endif %} have access to the runner group. To change which repositories and workflows can access the runner group, organization owners{% ifversion custom-org-roles %} and users with the “Manage organization runners and runner groups” permission{% endif %} can set a policy for the organization. For more information, see "[AUTOTITLE](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#disabling-repository-level-self-hosted-runners)."
 
 All organizations have a single default runner group. {% ifversion fpt %}Organization owners using the {% data variables.product.prodname_team %} plan{% else %}Organization owners{% ifversion custom-org-roles %} and users with the "Manage organization runners and runner groups" permission{% endif %}{% endif %} can create additional organization-level runner groups. {% ifversion custom-org-roles %}For more information about custom organization roles, see "[AUTOTITLE](/organizations/managing-peoples-access-to-your-organization-with-roles/about-custom-organization-roles)."{% endif %}
 

data/reusables/actions/custom-deployment-protection-rules-beta-note.md

@@ -1,5 +1,2 @@
-{% note %}
-
-**Note:** Custom deployment protection rules are currently in {% data variables.release-phases.public_preview %} and subject to change.
-
-{% endnote %}
+> [!NOTE]
+> Custom deployment protection rules are currently in {% data variables.release-phases.public_preview %} and subject to change.

data/reusables/actions/custom-deployment-protection-rules-limits.md

@@ -1,5 +1,2 @@
-{% note %}
-
-**Note:** Any number of {% data variables.product.prodname_github_apps %}-based deployment protection rules can be installed on a repository. However, a maximum of 6 deployment protection rules can be enabled on any environment at the same time.
-
-{% endnote %}
+> [!NOTE]
+> Any number of {% data variables.product.prodname_github_apps %}-based deployment protection rules can be installed on a repository. However, a maximum of 6 deployment protection rules can be enabled on any environment at the same time.

data/reusables/actions/docker-container-os-support.md

@@ -1,8 +1,5 @@
-{% note %}
-
-**Note:** If your workflows use Docker container actions, job containers, or service containers, then you must use a Linux runner:
-
-* If you are using {% data variables.product.prodname_dotcom %}-hosted runners, you must use an Ubuntu runner.
-* If you are using self-hosted runners, you must use a Linux machine as your runner and Docker must be installed.
-
-{% endnote %}
+> [!NOTE]
+> If your workflows use Docker container actions, job containers, or service containers, then you must use a Linux runner:
+>
+> * If you are using {% data variables.product.prodname_dotcom %}-hosted runners, you must use an Ubuntu runner.
+> * If you are using self-hosted runners, you must use a Linux machine as your runner and Docker must be installed.

data/reusables/actions/enterprise-common-prereqs.md

@@ -1,9 +1,7 @@
 * Review the hardware requirements for {% data variables.product.prodname_actions %}. For more information, see "[AUTOTITLE](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)."
 * TLS must be configured for {% data variables.product.prodname_ghe_server %}'s domain. For more information, see "[AUTOTITLE](/admin/configuration/configuring-network-settings/configuring-tls)."
 
-  {% note %}
+  > [!NOTE]
+  > {% data reusables.actions.enterprise-self-signed-cert %}
 
-  **Note:** {% data reusables.actions.enterprise-self-signed-cert %}
-
-  {% endnote %}
 * {% data reusables.actions.enterprise-http-proxy %}