Merge pull request github#27823 from github/repo-sync

Repo sync

content/actions/creating-actions/creating-a-docker-container-action.md

@@ -17,7 +17,7 @@ topics:
   - Action development
   - Docker
 ---
- 
+
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
 ## Introduction
@@ -32,26 +32,9 @@ Once you complete this project, you should understand how to build your own Dock
 
 ## Prerequisites
 
-You may find it helpful to have a basic understanding of {% data variables.product.prodname_actions %} environment variables and the Docker container filesystem:
-
-- "[AUTOTITLE](/actions/learn-github-actions/variables)"
-{% ifversion ghae %}
-- "[AUTOTITLE](/actions/hosting-your-own-runners#docker-container-filesystem)."
-{% else %}
-- "[AUTOTITLE](/actions/using-github-hosted-runners/about-github-hosted-runners#docker-container-filesystem)"
-{% endif %}
-
-Before you begin, you'll need to create a {% data variables.product.prodname_dotcom %} repository.
-
-1. Create a new repository on {% data variables.location.product_location %}. You can choose any repository name or use "hello-world-docker-action" like this example. For more information, see "[AUTOTITLE](/repositories/creating-and-managing-repositories/creating-a-new-repository)."
-
-1. Clone your repository to your computer. For more information, see "[AUTOTITLE](/repositories/creating-and-managing-repositories/cloning-a-repository)."
-
-1. From your terminal, change directories into your new repository.
-
-   ```shell copy
-   cd hello-world-docker-action
-   ```
+- You must create a repository on {% data variables.location.product_location %} and clone it to your workstation. For more information, see "[AUTOTITLE](/repositories/creating-and-managing-repositories/creating-a-new-repository)" and "[AUTOTITLE](/repositories/creating-and-managing-repositories/cloning-a-repository)."
+- If your repository uses {% data variables.large_files.product_name_short %}, you must include the objects in archives of your repository. For more information, see "[AUTOTITLE](/enterprise-cloud@latest/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-git-lfs-objects-in-archives-of-your-repository)."
+- You may find it helpful to have a basic understanding of {% data variables.product.prodname_actions %}, environment variables and the Docker container filesystem. For more information, see "[AUTOTITLE](/actions/learn-github-actions/variables)" and "[AUTOTITLE](/enterprise-cloud@latest/actions/using-github-hosted-runners/about-github-hosted-runners#docker-container-filesystem)."
 
 ## Creating a Dockerfile
 

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

@@ -17,7 +17,7 @@ topics:
   - Fundamentals
 layout: inline
 ---
- 
+
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
 ## Overview
@@ -90,10 +90,6 @@ For more information, see "[AUTOTITLE](/actions/creating-actions)."
 
 {% data reusables.actions.onboarding-next-steps %}
 
-## Contacting support
-
-{% data reusables.actions.contacting-support %}
-
 {% ifversion ghec or ghes or ghae %}
 
 ## Further reading

content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md

@@ -32,7 +32,7 @@ This guide shows you how to apply a centralized management approach to self-host
 1. Deploy a self-hosted runner for your enterprise
 1. Create a group to manage access to the runners available to your enterprise
 1. Optionally, further restrict the repositories that can use the runner
-1. Optionally, build custom tooling to automatically scale your self-hosted runners
+1. Optionally, {% ifversion actions-runner-controller %}to build and scale self-hosted runners automatically, use {% data variables.product.prodname_actions_runner_controller %} (ARC). For more information, see "[AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners-with-actions-runner-controller/about-actions-runner-controller)."{% else %}build custom tooling to automatically scale your self-hosted runners{% endif %}
 
 You'll also find additional information about how to monitor and secure your self-hosted runners,{% ifversion ghes or ghae %} how to access actions from {% data variables.product.prodname_dotcom_the_website %},{% endif %} and how to customize the software on your runner machines.
 
@@ -107,8 +107,10 @@ Optionally, organization owners can further restrict the access policy of the ru
 For more information, see "[AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)."
 
 ## 5. Automatically scale your self-hosted runners
+{% ifversion actions-runner-controller %}Optionally, you can use {% data variables.product.prodname_actions_runner_controller %} (ARC) to automatically scale self-hosted runners. {% data reusables.actions.actions-runner-controller-about-arc %}
 
-Optionally, you can build custom tooling to automatically scale the self-hosted runners for {% ifversion ghec or ghae %}your enterprise{% elsif ghes %}{% data variables.location.product_location %}{% endif %}. For example, your tooling can respond to webhook events from {% data variables.location.product_location %} to automatically scale a cluster of runner machines. For more information, see "[AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/autoscaling-with-self-hosted-runners)."
+{% else %}Optionally, you can build custom tooling to automatically scale the self-hosted runners for {% ifversion ghec or ghae %}your enterprise{% elsif ghes %}{% data variables.location.product_location %}{% endif %}. For example, your tooling can respond to webhook events from {% data variables.location.product_location %} to automatically scale a cluster of runner machines. For more information, see "[AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/autoscaling-with-self-hosted-runners)."
+{% endif %}
 
 ## Next steps
 

data/features/actions-runner-controller.yml

@@ -0,0 +1,6 @@
+# Reference: #8889
+# Feature based versioning file for Actions Runner Controller
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>= 3.9'

src/audit-logs/lib/config.json

@@ -1,3 +1,3 @@
 {
-  "sha": "7f0ca9729e8d76971b9710c69b03b89a048b6fad"
+  "sha": "8dafd521c21c65f3c9a5d766723d16be13e7dd60"
 }