github · docs-bot · Jul 21, 2025 · Jul 21, 2025 · Jul 21, 2025 · Jul 21, 2025
diff --git a/content/actions/concepts/runners/about-larger-runners.md b/content/actions/concepts/runners/about-larger-runners.md
diff --git a/content/actions/concepts/workflows-and-actions/about-custom-actions.md b/content/actions/concepts/workflows-and-actions/about-custom-actions.md
@@ -1,5 +1,6 @@
 ---
 title: About custom actions
+shortTitle: Custom actions
 intro: 'Actions are individual tasks that you can combine to create jobs and customize your workflow. You can create your own actions, or use and customize actions shared by the {% data variables.product.prodname_dotcom %} community.'
 redirect_from:
   - /articles/about-actions

diff --git a/content/actions/concepts/workflows-and-actions/about-monitoring-workflows.md b/content/actions/concepts/workflows-and-actions/about-monitoring-workflows.md
diff --git a/content/actions/concepts/workflows-and-actions/index.md b/content/actions/concepts/workflows-and-actions/index.md
@@ -17,7 +17,5 @@ children:
   - /concurrency
   - /workflow-artifacts
   - /dependency-caching
-  - /about-monitoring-workflows
   - /notifications-for-workflow-runs
-  - /about-troubleshooting-workflows
 ---
diff --git a/content/actions/concepts/workflows-and-actions/reusable-workflows.md b/content/actions/concepts/workflows-and-actions/reusable-workflows.md
@@ -36,7 +36,15 @@ Reusable workflows and composite actions both help you to avoid duplication. Whe
 
 ## Reusable workflows and workflow templates
 
-Workflow templates allow everyone in your organization who has permission to create workflows to do so more quickly and easily. When people create a new workflow, they can choose a workflow template and some or all of the work of writing the workflow will be done for them. Within a workflow template, you can also reference reusable workflows to make it easy for people to benefit from reusing centrally managed workflow code. If you use a commit SHA when referencing the reusable workflow, you can ensure that everyone who reuses that workflow will always be using the same YAML code. However, if you reference a reusable workflow by a tag or branch, be sure that you can trust that version of the workflow. For more information, see [AUTOTITLE](/actions/security-guides/security-hardening-for-github-actions#reusing-third-party-workflows).
+Workflow templates allow everyone in your organization who has permission to create workflows to do so more quickly and easily. When people create a new workflow, they can choose a workflow template and some or all of the work of writing the workflow will be done for them. Within a workflow template, you can also reference reusable workflows to make it easy for people to benefit from reusing centrally managed workflow code.
+
+If you use a commit SHA when referencing the reusable workflow, you can ensure that everyone who reuses that workflow will always be using the same YAML code. However, if you reference a reusable workflow by a tag or branch, be sure that you can trust that version of the workflow. For more information, see [AUTOTITLE](/actions/security-guides/security-hardening-for-github-actions#reusing-third-party-workflows).
+
+{% data variables.product.github %} offers workflow templates for a variety of languages and tooling. When you set up workflows in your repository, {% data variables.product.github %} analyzes the code in your repository and recommends workflows based on the language and framework in your repository. For example, if you use Node.js, {% data variables.product.github %} will suggest a workflow template file that installs your Node.js packages and runs your tests. You can search and filter to find relevant workflow templates.
+
+{% data reusables.actions.workflow-templates-categories %}
+
+{% data reusables.actions.workflow-templates-repo-link %}
 
 For more information, see [AUTOTITLE](/actions/using-workflows/creating-starter-workflows-for-your-organization).
 

diff --git a/...orking-with-support-for-github-actions.md → ...om-github-support-about-github-actions.md b/...orking-with-support-for-github-actions.md → ...om-github-support-about-github-actions.md
@@ -1,5 +1,6 @@
 ---
-title: Working with Support for GitHub Actions
+title: Getting help from GitHub Support about GitHub Actions
+shortTitle: Get support
 intro: 'Learn how {% data variables.contact.github_support %} can assist with {% data variables.product.prodname_actions %}'
 versions:
   fpt: '*'
@@ -9,10 +10,10 @@ type: reference
 topics:
   - Actions
   - Support
-shortTitle: 'Working with {% data variables.contact.github_support %}'
 redirect_from:
   - /actions/monitoring-and-troubleshooting-workflows/working-with-support-for-github-actions
   - /actions/monitoring-and-troubleshooting-workflows/troubleshooting-workflows/working-with-support-for-github-actions
+  - /actions/how-tos/monitoring-and-troubleshooting-workflows/troubleshooting-workflows/working-with-support-for-github-actions
 ---
 
 You can [contact {% data variables.contact.github_support %}](/support/contacting-github-support) for assistance with {% data variables.product.prodname_actions %}.

diff --git a/content/actions/how-tos/index.md b/content/actions/how-tos/index.md
@@ -10,11 +10,17 @@ children:
   - /writing-workflows
   - /managing-workflow-runs-and-deployments
   - /sharing-automations
-  - /monitoring-and-troubleshooting-workflows
   - /using-github-hosted-runners
+  - /using-larger-runners
   - /hosting-your-own-runners
   - /security-for-github-actions
   - /use-cases-and-examples
   - /administering-github-actions
+  - /monitor-workflows
+  - /troubleshooting-workflows
+  - /getting-help-from-github-support-about-github-actions
+redirect_from:
+  - /actions/how-tos/monitoring-and-troubleshooting-workflows
+  - /actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting
 ---
 
diff --git a/...ow-runs-and-deployments/managing-workflow-runs/re-running-workflows-and-jobs.md b/...ow-runs-and-deployments/managing-workflow-runs/re-running-workflows-and-jobs.md
@@ -13,11 +13,8 @@ versions:
   ghec: '*'
 ---
 
-{% data reusables.actions.enterprise-github-hosted-runners %}
-
-## About re-running workflows and jobs
-
-Re-running a workflow or jobs in a workflow uses the same `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (Git ref) of the original event that triggered the workflow run. The workflow will use the privileges of the actor who initially triggered the workflow, not the privileges of the actor who initiated the re-run. You can re-run a workflow or jobs in a workflow for up to 30 days after the initial run. You cannot re-run jobs in a workflow once its logs have passed their retention limits. For more information, see [AUTOTITLE](/actions/learn-github-actions/usage-limits-billing-and-administration#artifact-and-log-retention-policy). When you re-run a workflow or jobs in a workflow, you can enable debug logging for the re-run. This will enable runner diagnostic logging and step debug logging for the re-run. For more information about debug logging, see [AUTOTITLE](/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging)
+> [!NOTE]
+> Re-run workflows use the privileges of the actor who initially triggered the workflow, not the privileges of the actor who initiated the re-run. The workflow will also use the same `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (git ref) of the original event that triggered the workflow run.
 
 ## Re-running all the jobs in a workflow
 
@@ -30,7 +27,6 @@ Re-running a workflow or jobs in a workflow uses the same `GITHUB_SHA` (commit S
 1. In the upper-right corner of the workflow, re-run jobs.
 
    * If any jobs failed, select the **{% octicon "sync" aria-hidden="true" aria-label="sync" %} Re-run jobs** dropdown menu and click **Re-run all jobs**.
-
    * If no jobs failed, click **Re-run all jobs**.
 
 {% data reusables.actions.enable-debug-logging %}
@@ -39,32 +35,28 @@ Re-running a workflow or jobs in a workflow uses the same `GITHUB_SHA` (commit S
 
 {% cli %}
 
-{% data reusables.cli.cli-learn-more %}
-
-To re-run a failed workflow run, use the `run rerun` subcommand. Replace `run-id` with the ID of the failed run that you want to re-run. If you don't specify a `run-id`, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a recent failed run.
+1. To re-run a failed workflow run, use the `run rerun` subcommand, replacing `RUN_ID` with the ID of the failed run that you want to re-run. If you don't specify a `run-id`, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a recent failed run.
 
-```shell
-gh run rerun RUN_ID
-```
+    ```shell copy
+    gh run rerun RUN_ID
+    ```
 
-{% data reusables.actions.enable-debug-logging-cli %}
+    {% data reusables.actions.enable-debug-logging-cli %}
 
-```shell
-gh run rerun RUN_ID --debug
-```
+    ```shell copy
+    gh run rerun RUN_ID --debug
+    ```
 
-To view the progress of the workflow run, use the `run watch` subcommand and select the run from the interactive list.
+1. To view the progress of the workflow run, use the `run watch` subcommand and select the run from the interactive list.
 
-```shell
-gh run watch
-```
+    ```shell copy
+    gh run watch
+    ```
 
 {% endcli %}
 
 ## Re-running failed jobs in a workflow
 
-If any jobs in a workflow run failed, you can re-run just the jobs that failed. When you re-run failed jobs in a workflow, a new workflow run will start for all failed jobs and their dependents. Any outputs for any successful jobs in the previous workflow run will be used for the re-run. Any artifacts that were created in the initial run will be available in the re-run. Any deployment protection rules that passed in the previous run will automatically pass in the re-run.
-
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -78,7 +70,7 @@ If any jobs in a workflow run failed, you can re-run just the jobs that failed.
 
 {% cli %}
 
-To re-run failed jobs in a workflow run, use the `run rerun` subcommand with the `--failed` flag. Replace `run-id` with the ID of the run for which you want to re-run failed jobs. If you don't specify a `run-id`, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a recent failed run.
+To re-run failed jobs in a workflow run, use the `run rerun` subcommand with the `--failed` flag. Replace `RUN_ID` with the ID of the run for which you want to re-run failed jobs. If you don't specify a `run-id`, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a recent failed run.
 
 ```shell
 gh run rerun RUN_ID --failed
@@ -94,8 +86,6 @@ gh run rerun RUN_ID --failed --debug
 
 ## Re-running a specific job in a workflow
 
-When you re-run a specific job in a workflow, a new workflow run will start for the job and any dependents. Any outputs for any other jobs in the previous workflow run will be used for the re-run. Any artifacts that were created in the initial run will be available in the re-run. Any deployment protection rules that passed in the previous run will automatically pass in the re-run.
-
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -110,7 +100,7 @@ When you re-run a specific job in a workflow, a new workflow run will start for
 
 {% cli %}
 
-To re-run a specific job in a workflow run, use the `run rerun` subcommand with the `--job` flag. Replace `job-id` with the ID of the job that you want to re-run.
+To re-run a specific job in a workflow run, use the `run rerun` subcommand with the `--job` flag. Replace `JOB_ID` with the ID of the job that you want to re-run.
 
 ```shell
 gh run rerun --job JOB_ID
@@ -124,14 +114,8 @@ gh run rerun --job JOB_ID --debug
 
 {% endcli %}
 
-## Re-running workflows and jobs with reusable workflows
-
-{% data reusables.actions.partial-reruns-with-reusable %}
-
 ## Reviewing previous workflow runs
 
-You can view the results from your previous attempts at running a workflow. You can also view previous workflow runs using the API. For more information, see [AUTOTITLE](/rest/actions/workflow-runs#get-a-workflow-run).
-
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow %}

diff --git a/...rkflows/adding-a-workflow-status-badge.md → ...rkflows/adding-a-workflow-status-badge.md b/...rkflows/adding-a-workflow-status-badge.md → ...rkflows/adding-a-workflow-status-badge.md
diff --git a/...oting-workflows/enabling-debug-logging.md → ...nitor-workflows/enabling-debug-logging.md b/...oting-workflows/enabling-debug-logging.md → ...nitor-workflows/enabling-debug-logging.md
diff --git a/...g-workflows/monitoring-workflows/index.md → ...ctions/how-tos/monitor-workflows/index.md b/...g-workflows/monitoring-workflows/index.md → ...ctions/how-tos/monitor-workflows/index.md
@@ -1,6 +1,5 @@
 ---
-title: Monitoring workflows
-shortTitle: Monitor
+title: Monitor workflows
 intro: 'You can monitor {% data variables.product.prodname_actions %} workflows by using tools like the visualization graph and run logs.'
 versions:
   fpt: '*'
@@ -12,6 +11,8 @@ children:
   - /viewing-job-execution-time
   - /adding-a-workflow-status-badge
   - /using-workflow-run-logs
+  - /enabling-debug-logging
 redirect_from:
   - /actions/monitoring-and-troubleshooting-workflows/monitoring-workflows
+  - /actions/concepts/workflows-and-actions/about-monitoring-workflows
 ---
diff --git a/...orkflows/using-the-visualization-graph.md → ...orkflows/using-the-visualization-graph.md b/...orkflows/using-the-visualization-graph.md → ...orkflows/using-the-visualization-graph.md
@@ -1,6 +1,6 @@
 ---
 title: Using the visualization graph
-shortTitle: Visualization graph
+shortTitle: Use the visualization graph
 intro: Every workflow run generates a real-time graph that illustrates the run progress. You can use this graph to monitor and debug workflows.
 redirect_from:
   - /actions/managing-workflow-runs/using-the-visualization-graph

diff --git a/...ring-workflows/using-workflow-run-logs.md → ...itor-workflows/using-workflow-run-logs.md b/...ring-workflows/using-workflow-run-logs.md → ...itor-workflows/using-workflow-run-logs.md
@@ -1,6 +1,6 @@
 ---
 title: Using workflow run logs
-shortTitle: Workflow run logs
+shortTitle: Use workflow run logs
 intro: 'You can view, search, and download the logs for each job in a workflow run.'
 redirect_from:
   - /actions/managing-workflow-runs/using-workflow-run-logs

diff --git a/...g-workflows/viewing-job-execution-time.md → ...r-workflows/viewing-job-execution-time.md b/...g-workflows/viewing-job-execution-time.md → ...r-workflows/viewing-job-execution-time.md
diff --git a/...workflows/viewing-workflow-run-history.md → ...workflows/viewing-workflow-run-history.md b/...workflows/viewing-workflow-run-history.md → ...workflows/viewing-workflow-run-history.md
@@ -1,6 +1,6 @@
 ---
 title: Viewing workflow run history
-shortTitle: Workflow run history
+shortTitle: View workflow run history
 intro: You can view logs for each run of a workflow. Logs include the status for each job and step in a workflow.
 redirect_from:
   - /actions/managing-workflow-runs/viewing-workflow-run-history

diff --git a/content/actions/how-tos/monitoring-and-troubleshooting-workflows/index.md b/content/actions/how-tos/monitoring-and-troubleshooting-workflows/index.md
diff --git a/...tos/monitoring-and-troubleshooting-workflows/troubleshooting-workflows/index.md b/...tos/monitoring-and-troubleshooting-workflows/troubleshooting-workflows/index.md
diff --git a/...-workflows/troubleshooting-workflows/using-copilot-to-troubleshoot-workflows.md b/...-workflows/troubleshooting-workflows/using-copilot-to-troubleshoot-workflows.md
diff --git a/...ctions/about-troubleshooting-workflows.md → ...ions/how-tos/troubleshooting-workflows.md b/...ctions/about-troubleshooting-workflows.md → ...ions/how-tos/troubleshooting-workflows.md
@@ -1,13 +1,15 @@
 ---
-title: About troubleshooting workflows
+title: Troubleshooting workflows
+shortTitle: Troubleshoot workflows
 intro: 'You can use the tools in {% data variables.product.prodname_actions %} to debug your workflows.'
 versions:
   fpt: '*'
   ghes: '*'
   ghec: '*'
-shortTitle: About troubleshooting
 redirect_from:
   - /actions/monitoring-and-troubleshooting-workflows/troubleshooting-workflows/about-troubleshooting-workflows
+  - /actions/how-tos/monitoring-and-troubleshooting-workflows/troubleshooting-workflows/using-copilot-to-troubleshoot-workflows
+  - /actions/how-tos/monitoring-and-troubleshooting-workflows/troubleshooting-workflows
 ---
 
 {% data reusables.actions.enterprise-github-hosted-runners %}
@@ -18,9 +20,16 @@ There are several ways you can troubleshoot failed workflow runs.
 
 {% ifversion copilot %}
 
+>[!NOTE] If you are on a {% data variables.copilot.copilot_free %} subscription, this will count towards your monthly chat message limit.
+
 ### Using {% data variables.product.prodname_copilot %}
 
-If a workflow run fails, you can open a chat with {% data variables.product.prodname_copilot %} for assistance resolving the error. See [AUTOTITLE](/actions/monitoring-and-troubleshooting-workflows/troubleshooting-workflows/using-copilot-to-troubleshoot-workflows).
+To open a chat with {% data variables.product.prodname_copilot %} about a failed workflow run, you can either:
+
+* Next to the failed check in the merge box, click **{% octicon "kebab-horizontal" aria-hidden="true" aria-label="kebab-horizontal" %}**, then click **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %} Explain error**.
+* In the merge box, click on the failed check. At the top of the workflow run summary page, click **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %} Explain error**.
+
+This opens a chat window with {% data variables.product.prodname_copilot %}, where it will provide instructions to resolve the issue.
 
 {% endif %}
 

diff --git a/content/actions/how-tos/using-github-hosted-runners/index.md b/content/actions/how-tos/using-github-hosted-runners/index.md
@@ -9,8 +9,7 @@ versions:
 children:
   - /using-github-hosted-runners
   - /customizing-github-hosted-runners
-  - /monitoring-your-current-jobs
-  - /using-larger-runners
+  - /viewing-your-current-jobs
   - /connecting-to-a-private-network
 redirect_from:
   - /actions/using-github-hosted-runners