Merge pull request #39393 from github/repo-sync

Repo sync

Author: docs-bot

assets/images/help/copilot/activity-report-enterprise.png

@@ -14,28 +14,6 @@ type: tutorial
 shortTitle: Use runners in a workflow
 ---
 
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-You can target self-hosted runners for use in a workflow based on the labels assigned to the runners, or their group membership, or a combination of these.
-
->[!IMPORTANT]Runner Scale Sets do not support multiple labels, only the name of the runner can be used in place of a label. See [AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners-with-actions-runner-controller/deploying-runner-scale-sets-with-actions-runner-controller).
-
-## About self-hosted runner labels
-
-Labels allow you to send workflow jobs to specific types of self-hosted runners, based on their shared characteristics. For example, if your job requires a particular hardware component or software package, you can assign a custom label to a runner and then configure your job to only execute on runners with that label.
-
-{% data reusables.actions.self-hosted-runner-labels-runs-on %}
-
-For information on creating custom and default labels, see [AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/using-labels-with-self-hosted-runners).
-
-## About self-hosted runner groups
-
-For self-hosted runners defined at the organization {% ifversion ghec or ghes %}or enterprise levels{% else %}level{% endif %}, you can group your runners with shared characteristics into a single runner group and then configure your job to target the runner group.
-
-To specify a self-hosted runner group for your job, configure `runs-on.group` in your workflow file.
-
-For information on creating and managing runner groups, see [AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/managing-access-to-self-hosted-runners-using-groups).
-
 {% ifversion repository-actions-runners %}
 
 ## Viewing available runners for a repository
@@ -99,16 +77,3 @@ These labels operate cumulatively, so a self-hosted runner must have all four la
 ## Using labels and groups to route jobs
 
 {% data reusables.actions.jobs.example-runs-on-labels-and-groups %}
-
-## Routing precedence for self-hosted runners
-
-When routing a job to a self-hosted runner, {% data variables.product.prodname_dotcom %} looks for a runner that matches the job's `runs-on` labels and groups:
-
-* If {% data variables.product.prodname_dotcom %} finds an online and idle runner that matches the job's `runs-on` labels and groups, the job is then assigned and sent to the runner.
-  * If the runner doesn't pick up the assigned job within 60 seconds, the job is re-queued so that a new runner can accept it.
-* If {% data variables.product.prodname_dotcom %} doesn't find an online and idle runner that matches the job's `runs-on` labels and groups, then the job will remain queued until a runner comes online.
-* If the job remains queued for more than 24 hours, the job will fail.
-
-## Workflow run continuity
-
-{% data reusables.actions.runner-workflow-continuity %}

assets/images/help/copilot/activity-report-non-ghe.png

@@ -10,7 +10,6 @@ redirect_from:
   - /actions/examples
   - /actions/use-cases-and-examples
 children:
-  - publishing-packages
   - project-management
   - using-containerized-services
 ---

assets/images/help/copilot/activity-report-org.png

@@ -15,7 +15,7 @@ featuredLinks:
     - /actions/how-tos/monitoring-and-troubleshooting-workflows
   guideCards:
     - /actions/how-tos/writing-workflows/using-workflow-templates
-    - /actions/how-tos/use-cases-and-examples/publishing-packages/publishing-nodejs-packages
+    - /actions/tutorials/publishing-packages/publishing-nodejs-packages
     - /actions/how-tos/writing-workflows/building-and-testing/building-and-testing-powershell
   popular:
     - /actions/reference/workflow-syntax-for-github-actions

content/actions/how-tos/hosting-your-own-runners/managing-self-hosted-runners/using-self-hosted-runners-in-a-workflow.md

@@ -58,6 +58,15 @@ You can use a machine as a self-hosted runner as long as it meets these requirem
 * `ARM64` - Linux, macOS{% ifversion actions-windows-arm %}, Windows (currently in {% data variables.release-phases.public_preview %}){% endif %}.
 * `ARM32` - Linux.
 
+## Routing precedence for self-hosted runners
+
+When routing a job to a self-hosted runner, {% data variables.product.prodname_dotcom %} looks for a runner that matches the job's `runs-on` labels and groups:
+
+* If {% data variables.product.prodname_dotcom %} finds an online and idle runner that matches the job's `runs-on` labels and groups, the job is then assigned and sent to the runner.
+  * If the runner doesn't pick up the assigned job within 60 seconds, the job is re-queued so that a new runner can accept it.
+* If {% data variables.product.prodname_dotcom %} doesn't find an online and idle runner that matches the job's `runs-on` labels and groups, then the job will remain queued until a runner comes online.
+* If the job remains queued for more than 24 hours, the job will fail.
+
 ## Autoscaling
 
 You can automatically increase or decrease the number of self-hosted runners in your environment in response to the webhook events you receive with a particular label.

content/actions/how-tos/use-cases-and-examples/index.md

@@ -17,6 +17,7 @@ children:
   - /store-and-share-data
   - /deploying-with-github-actions
   - /communicating-with-docker-service-containers
+  - /publishing-packages
 redirect_from:
   - /actions/guides
 ---

content/actions/index.md

@@ -10,6 +10,7 @@ redirect_from:
   - /actions/publishing-packages-with-github-actions
   - /actions/publishing-packages
   - /actions/use-cases-and-examples/publishing-packages
+  - /actions/how-tos/use-cases-and-examples/publishing-packages
 children:
   - /publishing-docker-images
   - /publishing-java-packages-with-gradle

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

@@ -1,12 +1,13 @@
 ---
 title: Publishing Docker images
 shortTitle: Publish Docker images
-intro: 'You can publish Docker images to a registry, such as Docker Hub or {% data variables.product.prodname_registry %}, as part of your continuous integration (CI) workflow.'
+intro: 'In this tutorial, you''ll learn how to publish Docker images to a registry, such as Docker Hub or {% data variables.product.prodname_registry %}, as part of your continuous integration (CI) workflow.'
 redirect_from:
   - /actions/language-and-framework-guides/publishing-docker-images
   - /actions/guides/publishing-docker-images
   - /actions/publishing-packages/publishing-docker-images
   - /actions/use-cases-and-examples/publishing-packages/publishing-docker-images
+  - /actions/how-tos/use-cases-and-examples/publishing-packages/publishing-docker-images
 versions:
   fpt: '*'
   ghes: '*'
@@ -19,8 +20,6 @@ topics:
 layout: inline
 ---
 
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
 ## Introduction
 
 This guide shows you how to create a workflow that performs a Docker build, and then publishes Docker images to Docker Hub or {% data variables.product.prodname_registry %}. With a single workflow, you can publish images to a single registry or to multiple registries.