EDI-ify About self-hosted runners + Supported architectures and operating systems for self-hosted runners (#56510)

Author: sabrowning1

content/actions/concepts/runners/about-self-hosted-runners.md

@@ -1,5 +1,6 @@
 ---
 title: About self-hosted runners
+shortTitle: Self-hosted runners
 intro: 'You can host your own runners and customize the environment used to run jobs in your {% data variables.product.prodname_actions %} workflows.'
 redirect_from:
   - /github/automating-your-workflow-with-github-actions/about-self-hosted-runners
@@ -13,14 +14,12 @@ versions:
 type: overview
 ---
 
-## About self-hosted runners
-
 A self-hosted runner is a system that you deploy and manage to execute jobs from {% data variables.product.prodname_actions %} on {% data variables.product.github %}.
 
 Self-hosted runners:
 
 {% ifversion fpt or ghec %}
-* Give you more control of hardware, operating system, and software tools than {% data variables.product.prodname_dotcom %}-hosted runners provide.{% endif %}
+* Give you more control of hardware, operating system, and software tools than {% data variables.product.prodname_dotcom %}-hosted runners provide. Be aware that you are responsible for updating the operating system and all other software.{% endif %}
 * Are free to use with {% data variables.product.prodname_actions %}, but you are responsible for the cost of maintaining your runner machines.
 * Let you create custom hardware configurations that meet your needs with processing power or memory to run larger jobs, install software available on your local network.
 * Receive automatic updates for the self-hosted runner application only, though you may disable automatic updates of the runner.
@@ -31,30 +30,12 @@ Self-hosted runners:
 
 You can use self-hosted runners anywhere in the management hierarchy. Repository-level runners are dedicated to a single repository, while organization-level runners can process jobs for multiple repositories in an organization. Organization owners can choose which repositories are allowed to create repository-level self-hosted runners. See [AUTOTITLE](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#limiting-the-use-of-self-hosted-runners). Finally, enterprise-level runners can be assigned to multiple organizations in an enterprise account.
 
-### Requirements for self-hosted runner machines
-
-You can use any machine as a self-hosted runner as long as it meets these requirements:
-
-* You can install and run the self-hosted runner application on the machine.
-* The machine can communicate with {% data variables.product.prodname_actions %}.
-* The machine has enough hardware resources for the type of workflows you plan to run. The self-hosted runner application itself only requires minimal resources.
-* If you want to run workflows that use Docker container actions or service containers, you must use a Linux machine and Docker must be installed.
-
-{% ifversion ghes %}
-
-## Supported actions on self-hosted runners
-
-All `actions/setup-LANGUAGE` action repositories currently support three platforms: macOS, Windows, and Ubuntu.
-Some extra configuration might be required to use actions from {% data variables.product.github %} with {% data variables.product.prodname_ghe_server %}, or to use the `actions/setup-LANGUAGE` actions with self-hosted runners that do not have internet access. For more information, see [AUTOTITLE](/admin/github-actions/managing-access-to-actions-from-githubcom) and contact your {% data variables.product.prodname_enterprise %} site administrator.
+## Next steps
 
+{% ifversion ghec or ghes %}
+To get hands-on experience with the policies and usage of self-hosted runners, see [AUTOTITLE](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise)
+{% else %}
+To set up a self-hosted runner in your workspace, see [AUTOTITLE](/actions/how-tos/hosting-your-own-runners/managing-self-hosted-runners/adding-self-hosted-runners).
 {% endif %}
 
-## Further reading
-
-* [AUTOTITLE](/actions/security-for-github-actions/security-guides/security-hardening-for-github-actions)
-* [AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/adding-self-hosted-runners)
-* [AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/using-self-hosted-runners-in-a-workflow)
-* [AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/autoscaling-with-self-hosted-runners){% ifversion ghec or ghes %}
-* [AUTOTITLE](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise){% endif %}
-* [AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/supported-architectures-and-operating-systems-for-self-hosted-runners)
-* [AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/communicating-with-self-hosted-runners)
+To find information about the requirements and supported software and hardware for self-hosted runners, see [AUTOTITLE](/actions/reference/self-hosted-runners-reference).

content/actions/reference/index.md

@@ -18,7 +18,8 @@ children:
   - /actions-limits
   - /dockerfile-support-for-github-actions
   - /github-hosted-runners-reference
-  - /supported-architectures-and-operating-systems-for-self-hosted-runners
+  - /self-hosted-runners-reference
   - /usage-limits-for-self-hosted-runners
   - /supplemental-arguments-and-settings
 ---
+

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

@@ -0,0 +1,54 @@
+---
+title: Self-hosted runners reference
+shortTitle: Self-hosted runners reference
+intro: Find information about requirements and supported actions for self-hosted runners.
+redirect_from:
+  - /actions/hosting-your-own-runners/managing-self-hosted-runners/supported-architectures-and-operating-systems-for-self-hosted-runners
+  - /actions/reference/supported-architectures-and-operating-systems-for-self-hosted-runners
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+type: overview
+---
+
+## Requirements for self-hosted runner machines
+
+You can use a machine as a self-hosted runner as long as it meets these requirements:
+
+* You can install and run the self-hosted runner application on the machine. See [Supported operating systems](#supported-operating-systems) and [Supported processor architectures](#supported-processor-architectures).
+* The machine can communicate with {% data variables.product.prodname_actions %}.
+* The machine has enough hardware resources for the type of workflows you plan to run. The self-hosted runner application itself only requires minimal resources.
+* If you want to run workflows that use Docker container actions or service containers, you must use a Linux machine and Docker must be installed.
+
+### Supported operating systems
+
+#### Linux
+
+* Red Hat Enterprise Linux 8 or later
+* CentOS 8 or later
+* Oracle Linux 8 or later
+* Fedora 29 or later
+* Debian 10 or later
+* Ubuntu 20.04 or later
+* Linux Mint 20 or later
+* openSUSE 15.2 or later
+* SUSE Enterprise Linux (SLES) 15 SP2 or later
+
+#### Windows
+
+* Windows 10 64-bit
+* Windows 11 64-bit
+* Windows Server 2016 64-bit
+* Windows Server 2019 64-bit
+* Windows Server 2022 64-bit
+
+#### macOS
+
+* macOS 11.0 (Big Sur) or later
+
+### Supported processor architectures
+
+* `x64` - Linux, macOS, Windows.
+* `ARM64` - Linux, macOS{% ifversion actions-windows-arm %}, Windows (currently in {% data variables.release-phases.public_preview %}){% endif %}.
+* `ARM32` - Linux.