[EDI] Concepts/Use cases (#56589)

Co-authored-by: Copilot <[email protected]>

Author: subatoi

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

@@ -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/use-cases/using-github-actions-for-project-management.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

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

@@ -1,5 +1,6 @@
 ---
 title: Deploying with GitHub Actions
+shortTitle: Controlling deployments
 intro: Learn how to control deployments with features like environments and concurrency.
 versions:
   fpt: '*'
@@ -10,24 +11,12 @@ redirect_from:
   - /actions/deployment/deploying-with-github-actions
   - /actions/deployment/about-deployments/deploying-with-github-actions
   - /actions/use-cases-and-examples/deploying/deploying-with-github-actions
+  - /actions/concepts/use-cases/deploying-with-github-actions
 topics:
   - CD
   - Deployment
-shortTitle: Deploy with GitHub Actions
 ---
 
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-## Introduction
-
-{% data variables.product.prodname_actions %} offers features that let you control deployments. You can:
-
-* Trigger workflows with a variety of events.
-* Configure environments to set rules before a job can proceed and to limit access to secrets.
-* Use concurrency to control the number of deployments running at a time.
-
-For more information about continuous deployment, see [AUTOTITLE](/actions/deployment/about-deployments/about-continuous-deployment).
-
 ## Prerequisites
 
 You should be familiar with the syntax for {% data variables.product.prodname_actions %}. For more information, see [AUTOTITLE](/actions/learn-github-actions).

content/actions/index.md

@@ -13,6 +13,8 @@ children:
   - /creating-a-javascript-action
   - /creating-a-composite-action
   - /quickstart-for-actions-runner-controller
+  - /deploying-with-github-actions
+  - /communicating-with-docker-service-containers
 redirect_from:
   - /actions/guides
 ---

content/actions/concepts/use-cases/about-service-containers.md renamed to content/actions/tutorials/communicating-with-docker-service-containers.md

@@ -23,7 +23,6 @@ redirect_from:
 | Automatically test and build your application | [AUTOTITLE](/actions/automating-builds-and-tests/about-continuous-integration) |
 | Deploy your application | [AUTOTITLE](/actions/deployment/about-deployments/about-continuous-deployment) |
 | Automatically and securely package code into artifacts and containers | [AUTOTITLE](/actions/publishing-packages/about-packaging-with-github-actions) |
-| Automate your project management tasks | [AUTOTITLE](/actions/managing-issues-and-pull-requests/using-github-actions-for-project-management) |
 
 {% data variables.product.prodname_actions %} helps your team work faster at scale. When large repositories start using {% data variables.product.prodname_actions %}, pull requests are typically merged faster, allowing teams to merge more pull requests per day.