Merge branch 'main' into patch-3

content/actions/index.md

@@ -46,6 +46,8 @@ versions:
 children:
   - /quickstart
   - /learn-github-actions
+  - /using-workflows
+  - /using-jobs
   - /managing-workflow-runs
   - /automating-builds-and-tests
   - /deployment

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

@@ -4,25 +4,15 @@ shortTitle: Learn GitHub Actions
 intro: 'Whether you are new to {% data variables.product.prodname_actions %} or interested in learning all they have to offer, this guide will help you use {% data variables.product.prodname_actions %} to accelerate your application development workflows.'
 redirect_from:
   - /articles/about-github-actions
-  - /github/automating-your-workflow-with-github-actions/about-github-actions
-  - /actions/automating-your-workflow-with-github-actions/about-github-actions
   - /actions/getting-started-with-github-actions
   - /actions/getting-started-with-github-actions/about-github-actions
   - /actions/getting-started-with-github-actions/overview
   - /actions/getting-started-with-github-actions/getting-started-with-github-actions
-  - /actions/configuring-and-managing-workflows/configuring-a-workflow
-  - /articles/creating-a-workflow-with-github-actions
-  - /articles/configuring-a-workflow
-  - /github/automating-your-workflow-with-github-actions/configuring-a-workflow
-  - /actions/automating-your-workflow-with-github-actions/configuring-a-workflow
-  - /actions/creating-workflows/workflow-configuration-options
-  - /articles/configuring-workflows
-  - /github/automating-your-workflow-with-github-actions/configuring-workflows
-  - /actions/automating-your-workflow-with-github-actions/configuring-workflows
+  - /articles/getting-started-with-github-actions
+  - /github/automating-your-workflow-with-github-actions/about-github-actions
+  - /actions/automating-your-workflow-with-github-actions/about-github-actions
   - /github/automating-your-workflow-with-github-actions/getting-started-with-github-actions
   - /actions/automating-your-workflow-with-github-actions/getting-started-with-github-actions
-  - /actions/configuring-and-managing-workflows
-  - /articles/getting-started-with-github-actions
 versions:
   fpt: '*'
   ghes: '*'
@@ -32,16 +22,8 @@ children:
   - /understanding-github-actions
   - /finding-and-customizing-actions
   - /essential-features-of-github-actions
-  - /managing-complex-workflows
-  - /sharing-workflows-secrets-and-runners-with-your-organization
-  - /creating-starter-workflows-for-your-organization
-  - /using-starter-workflows
-  - /reusing-workflows
-  - /events-that-trigger-workflows
   - /expressions
   - /contexts
-  - /workflow-syntax-for-github-actions
-  - /workflow-commands-for-github-actions
   - /environment-variables
   - /usage-limits-billing-and-administration
 ---

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

@@ -42,6 +42,8 @@ Your repository can have multiple workflows in a repository, each of which can p
 
 {% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}You can reference a workflow within another workflow, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."{% endif %}
 
+For more information about workflows, see "[Using workflows](/actions/using-workflows)."
+
 ### Events
 
 An event is a specific activity in a repository that triggers a workflow run. For example, activity can originate from {% data variables.product.prodname_dotcom %} when someone creates a pull request, opens an issue, or pushes a commit to a repository.  You can also trigger a workflow run on a schedule, by [posting to a REST API](/rest/reference/repos#create-a-repository-dispatch-event), or manually.
@@ -54,12 +56,16 @@ A job is a set of _steps_ in a workflow that execute on the same runner.  Each s
 
 You can configure a job's dependencies with other jobs; by default, jobs have no dependencies and run in parallel with each other.  When a job takes a dependency on another job, it will wait for the dependent job to complete before it can run.  For example, you may have multiple build jobs for different architectures that have no dependencies, and a packaging job that is dependent on those jobs.  The build jobs will run in parallel, and when they have all completed successfully, the packaging job will run.
 
+For more information about jobs, see "[Using jobs](/actions/using-jobs)."
+
 ### Actions
 
 An _action_ is a custom application for the {% data variables.product.prodname_actions %} platform that performs a complex but frequently repeated task.  Use an action to help reduce the amount of repetitive code that you write in your workflow files.  An action can pull your git repository from {% data variables.product.prodname_dotcom %}, set up the correct toolchain for your build environment, or set up the authentication to your cloud provider.
 
 You can write your own actions, or you can find actions to use in your workflows in the {% data variables.product.prodname_marketplace %}.
 
+For more information, see "[Creating actions](/actions/creating-actions)."
+
 ### Runners
 
 {% data reusables.actions.about-runners %} Each runner can run a single job at a time. {% ifversion ghes or ghae %} You must host your own runners for {% data variables.product.product_name %}. {% elsif fpt or ghec %}{% data variables.product.company_short %} provides Ubuntu Linux, Microsoft Windows, and macOS runners to run your workflows; each workflow run executes in a fresh, newly-provisioned virtual machine. If you need a different operating system or require a specific hardware configuration, you can host your own runners.{% endif %} For more information{% ifversion fpt or ghec %} about self-hosted runners{% endif %}, see "[Hosting your own runners](/actions/hosting-your-own-runners)."