Merge pull request #39267 from github/repo-sync

Repo sync

Author: docs-bot

content/actions/concepts/index.md

@@ -11,6 +11,7 @@ children:
   - /workflows-and-actions
   - /runners
   - /security
-  - /use-cases
   - /about-github-actions-metrics
+redirect_from:
+  - /actions/concepts/use-cases
 ---

content/actions/concepts/use-cases/about-packaging-with-github-actions.md

@@ -13,6 +13,7 @@ redirect_from:
   - /actions/using-workflows/advanced-workflow-features
   - /actions/using-workflows/about-workflows
   - /actions/writing-workflows/about-workflows
+  - /actions/concepts/use-cases/using-github-actions-for-project-management
 topics:
   - Workflows
 layout: inline

content/actions/concepts/use-cases/index.md

@@ -1,7 +1,7 @@
 ---
 title: How-tos for GitHub Actions
 shortTitle: How-tos
-intro: "Learn how to accomplish specific goals with GitHub Actions."
+intro: Learn how to accomplish specific goals with GitHub Actions.
 versions:
   fpt: '*'
   ghes: '*'
@@ -15,6 +15,6 @@ children:
   - /hosting-your-own-runners
   - /security-for-github-actions
   - /use-cases-and-examples
-  - /migrating-to-github-actions
   - /administering-github-actions
----
+---
+

content/actions/concepts/use-cases/using-github-actions-for-project-management.md

@@ -10,8 +10,8 @@ featuredLinks:
     - /actions/how-tos/writing-workflows
     - /actions/how-tos/use-cases-and-examples
     - /actions/concepts/overview/continuous-integration
-    - /actions/concepts/use-cases/deploying-with-github-actions
-    - /actions/concepts/use-cases/about-packaging-with-github-actions
+    - /actions/tutorials/deploying-with-github-actions
+    - /packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions
     - /actions/how-tos/monitoring-and-troubleshooting-workflows
   guideCards:
     - /actions/how-tos/writing-workflows/using-workflow-templates

content/actions/concepts/workflows-and-actions/about-workflows.md

@@ -14,6 +14,7 @@ shortTitle: Extending GitHub Actions Importer
 redirect_from:
   - /actions/migrating-to-github-actions/automated-migrations/extending-github-actions-importer-with-custom-transformers
   - /actions/migrating-to-github-actions/using-github-actions-importer-to-automate-migrations/extending-github-actions-importer-with-custom-transformers
+  - /actions/how-tos/migrating-to-github-actions/using-github-actions-importer-to-automate-migrations/extending-github-actions-importer-with-custom-transformers
 ---
 
 [Legal notice](#legal-notice)

content/actions/how-tos/index.md

@@ -26,4 +26,6 @@ children:
   - /self-hosted-runners-reference
   - /usage-limits-for-self-hosted-runners
   - /supplemental-arguments-and-settings
+  - /extending-github-actions-importer-with-custom-transformers
 ---
+

content/actions/index.md

@@ -1,12 +1,14 @@
 ---
-title: About service containers
-intro: 'You can use service containers to connect databases, web services, memory caches, and other tools to your workflow.'
+title: Communicating with Docker service containers
+shortTitle: Docker service containers
+intro: Learn how to use Docker service containers to connect databases, web services, memory caches, and other tools to your workflow.
 redirect_from:
   - /actions/automating-your-workflow-with-github-actions/about-service-containers
   - /actions/configuring-and-managing-workflows/about-service-containers
   - /actions/guides/about-service-containers
   - /actions/using-containerized-services/about-service-containers
   - /actions/use-cases-and-examples/using-containerized-services/about-service-containers
+  - /actions/concepts/use-cases/about-service-containers
 versions:
   fpt: '*'
   ghes: '*'
@@ -17,18 +19,14 @@ topics:
   - Docker
 ---
 
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-## About service containers
+## Communicating with Docker service containers
 
 Service containers are Docker containers that provide a simple and portable way for you to host services that you might need to test or operate your application in a workflow. For example, your workflow might need to run integration tests that require access to a database and memory cache.
 
 You can configure service containers for each job in a workflow. {% data variables.product.prodname_dotcom %} creates a fresh Docker container for each service configured in the workflow, and destroys the service container when the job completes. Steps in a job can communicate with all service containers that are part of the same job. However, you cannot create and use service containers inside a composite action.
 
 {% data reusables.actions.docker-container-os-support %}
 
-## Communicating with service containers
-
 You can configure jobs in a workflow to run directly on a runner machine or in a Docker container. Communication between a job and its service containers is different depending on whether a job runs directly on the runner machine or in a container.
 
 ### Running jobs in a container