Update redirected internal links in data/reusables (actions (part 2)) (#62169)

heiskr · Copilot · web-flow · commit 8c0c8abc960d · 2026-07-09T18:30:19.000Z
Co-authored-by: Copilot &lt;223556219+Copilot@users.noreply.github.com&gt;
diff --git a/data/reusables/actions/viewing-actions-metrics.md b/data/reusables/actions/viewing-actions-metrics.md
@@ -1,6 +1,6 @@
 1. In the "Insights" navigation menu, click **Actions Usage Metrics** or click **Actions Performance Metrics**.
-1. Optionally, to select a time period to view usage metrics for, choose an option from the **Period** drop down menu at the top right of the page. For more information, see [AUTOTITLE](/actions/how-tos/administering-github-actions/viewing-github-actions-metrics#understanding-github-actions-metrics-aggregation).
-1. Click on the tab that contains the metrics you would like to view. For more information, see [AUTOTITLE](/actions/concepts/about-github-actions-metrics).
+1. Optionally, to select a time period to view usage metrics for, choose an option from the **Period** drop down menu at the top right of the page. For more information, see [AUTOTITLE](/actions/how-tos/administer/view-metrics#understanding-github-actions-metrics-aggregation).
+1. Click on the tab that contains the metrics you would like to view. For more information, see [AUTOTITLE](/actions/concepts/metrics).
 1. Optionally, to filter the data displayed in a tab, create a filter.
     1. Click on the **{% octicon "filter" aria-hidden="true" aria-label="filter" %} Filter** button.
     1. Click **{% octicon "plus" aria-hidden="true" aria-label="plus" %} Add a filter**.
diff --git a/data/reusables/actions/workflow-basic-example-and-explanation.md b/data/reusables/actions/workflow-basic-example-and-explanation.md
@@ -70,7 +70,7 @@ jobs:
 
 ### Visualizing the workflow file
 
-In this diagram, you can see the workflow file you just created and how the {% data variables.product.prodname_actions %} components are organized in a hierarchy. Each step executes a single action or shell script. Steps 1 and 2 run actions, while steps 3 and 4 run shell scripts. To find more prebuilt actions for your workflows, see [AUTOTITLE](/actions/learn-github-actions/finding-and-customizing-actions).
+In this diagram, you can see the workflow file you just created and how the {% data variables.product.prodname_actions %} components are organized in a hierarchy. Each step executes a single action or shell script. Steps 1 and 2 run actions, while steps 3 and 4 run shell scripts. To find more prebuilt actions for your workflows, see [AUTOTITLE](/actions/how-tos/write-workflows/choose-what-workflows-do/find-and-customize-actions).
 
 ![Diagram showing the trigger, runner, and job of a workflow. The job is broken into 4 steps.](/assets/images/help/actions/overview-actions-event.png)
 
diff --git a/data/reusables/actions/workflow-dispatch-inputs.md b/data/reusables/actions/workflow-dispatch-inputs.md
@@ -1,3 +1,3 @@
-The triggered workflow receives the inputs in the `inputs` context. For more information, see [Contexts](/actions/learn-github-actions/contexts#inputs-context).
+The triggered workflow receives the inputs in the `inputs` context. For more information, see [Contexts](/actions/reference/workflows-and-actions/contexts#inputs-context).
 
 {% data reusables.actions.inputs-vs-github-event-inputs %}
diff --git a/data/reusables/actions/workflow-permissions-intro.md b/data/reusables/actions/workflow-permissions-intro.md
@@ -1 +1 @@
-You can set the default permissions granted to the `GITHUB_TOKEN`. For more information about the `GITHUB_TOKEN`, see [AUTOTITLE](/actions/security-guides/automatic-token-authentication). You can choose a restricted set of permissions as the default, or apply permissive settings.
+You can set the default permissions granted to the `GITHUB_TOKEN`. For more information about the `GITHUB_TOKEN`, see [AUTOTITLE](/actions/tutorials/authenticate-with-github_token). You can choose a restricted set of permissions as the default, or apply permissive settings.
diff --git a/data/reusables/actions/workflow-permissions-modifying.md b/data/reusables/actions/workflow-permissions-modifying.md
@@ -1 +1 @@
-Anyone with write access to a repository can modify the permissions granted to the `GITHUB_TOKEN`, adding or removing access as required, by editing the `permissions` key in the workflow file. For more information, see [`permissions`](/actions/using-workflows/workflow-syntax-for-github-actions#permissions).
+Anyone with write access to a repository can modify the permissions granted to the `GITHUB_TOKEN`, adding or removing access as required, by editing the `permissions` key in the workflow file. For more information, see [`permissions`](/actions/reference/workflows-and-actions/workflow-syntax#permissions).
diff --git a/data/reusables/actions/workflow-run-approve-link.md b/data/reusables/actions/workflow-run-approve-link.md
@@ -1 +1 @@
-For more information about approving workflow runs that this policy applies to, see [AUTOTITLE](/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks).
+For more information about approving workflow runs that this policy applies to, see [AUTOTITLE](/actions/how-tos/manage-workflow-runs/approve-runs-from-forks).
diff --git a/data/reusables/actions/workflow-run-approve-public-fork.md b/data/reusables/actions/workflow-run-approve-public-fork.md
@@ -7,6 +7,6 @@ To help prevent this, workflows on pull requests to public repositories from som
 
 By default, all first-time contributors require approval to run workflows.
 
-Workflows triggered by `pull_request_target` events are run in the context of the base branch. Since the base branch is considered trusted, workflows triggered by these events will always run, regardless of approval settings. For more information about the `pull_request_target` event, see [AUTOTITLE](/actions/using-workflows/events-that-trigger-workflows#pull_request_target).
+Workflows triggered by `pull_request_target` events are run in the context of the base branch. Since the base branch is considered trusted, workflows triggered by these events will always run, regardless of approval settings. For more information about the `pull_request_target` event, see [AUTOTITLE](/actions/reference/workflows-and-actions/events-that-trigger-workflows#pull_request_target).
 
->[!WARNING] These workflow approval policies are intended to restrict the set of users that can execute workflows in {% data variables.product.prodname_actions %} runners that could lead to unexpected resource and compute consumption when using {% data variables.product.prodname_dotcom %}-hosted runners. If you are using self-hosted runners, potentially malicious user-controlled workflow code will execute automatically if the user is allowed to bypass approval in the set approval policy or if the pull request is approved. You must consider the risk of executing this code in your infrastructure and should review and follow the self-hosted runner security recommendations regardless of the approval settings utilized. See [AUTOTITLE](/actions/security-for-github-actions/security-guides/security-hardening-for-github-actions#hardening-for-self-hosted-runners).
+> [!WARNING] These workflow approval policies are intended to restrict the set of users that can execute workflows in {% data variables.product.prodname_actions %} runners that could lead to unexpected resource and compute consumption when using {% data variables.product.prodname_dotcom %}-hosted runners. If you are using self-hosted runners, potentially malicious user-controlled workflow code will execute automatically if the user is allowed to bypass approval in the set approval policy or if the pull request is approved. You must consider the risk of executing this code in your infrastructure and should review and follow the self-hosted runner security recommendations regardless of the approval settings utilized. See [AUTOTITLE](/actions/reference/security/secure-use#hardening-for-self-hosted-runners).
diff --git a/data/reusables/actions/workflow-runs-dependabot-note.md b/data/reusables/actions/workflow-runs-dependabot-note.md
@@ -1 +1 @@
-Workflow runs triggered by {% data variables.product.prodname_dependabot %} pull requests run as if they are from a forked repository, and therefore use a read-only `GITHUB_TOKEN`. These workflow runs cannot access any secrets. For information about strategies to keep these workflows secure, see [AUTOTITLE](/actions/security-guides/security-hardening-for-github-actions).
+Workflow runs triggered by {% data variables.product.prodname_dependabot %} pull requests run as if they are from a forked repository, and therefore use a read-only `GITHUB_TOKEN`. These workflow runs cannot access any secrets. For information about strategies to keep these workflows secure, see [AUTOTITLE](/actions/reference/security/secure-use).
diff --git a/data/reusables/actions/workflow-templates-categories.md b/data/reusables/actions/workflow-templates-categories.md
@@ -1,5 +1,5 @@
 {% data variables.product.prodname_dotcom %} provides ready-to-use workflow templates for the following high level categories:
-* **Deployment (CD)**. For more information, see [AUTOTITLE](/actions/deployment/about-deployments/about-continuous-deployment).
-{% ifversion fpt or ghec %}- **Security**. For more information, see [AUTOTITLE](/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/configuring-advanced-setup-for-code-scanning#configuring-code-scanning-using-third-party-actions).{% endif %}
-* **Continuous Integration (CI)**. For more information, see [AUTOTITLE](/actions/automating-builds-and-tests/about-continuous-integration).
+* **Deployment (CD)**. For more information, see [AUTOTITLE](/actions/get-started/continuous-deployment).
+{% ifversion fpt or ghec %}* **Security**. For more information, see [AUTOTITLE](/code-security/how-tos/find-and-fix-code-vulnerabilities/configure-code-scanning/configuring-advanced-setup-for-code-scanning#configuring-code-scanning-using-third-party-actions).{% endif %}
+* **Continuous Integration (CI)**. For more information, see [AUTOTITLE](/actions/get-started/continuous-integration).
 * **Automation**. Automation workflow templates offer solutions for automating workflows, such as triaging pull requests and applying a label based on the paths that are modified in the pull request, or greeting users who are first time contributors to the repository.
diff --git a/data/reusables/actions/workflow-templates-for-more-information.md b/data/reusables/actions/workflow-templates-for-more-information.md
@@ -1 +1 @@
-To get started with preconfigured workflows, browse through the list of templates in the [actions/starter-workflows](https://github.com/actions/starter-workflows) repository. For more information, see [AUTOTITLE](/actions/writing-workflows/using-starter-workflows).
+To get started with preconfigured workflows, browse through the list of templates in the [actions/starter-workflows](https://github.com/actions/starter-workflows) repository. For more information, see [AUTOTITLE](/actions/how-tos/write-workflows/use-workflow-templates).
diff --git a/data/reusables/actions/workflows-from-public-fork-setting.md b/data/reusables/actions/workflows-from-public-fork-setting.md
@@ -1,4 +1,4 @@
-1. Under **Approval for running fork pull request workflows from contributors**, choose which subset of users will require approval before running workflows on their pull requests. Both the pull request author and the actor of the pull request event triggering the workflow will be checked to determine if approval is required. If approval is required, a user with write access to the repository must approve the pull request workflow to be run. See [AUTOTITLE](/actions/managing-workflow-runs-and-deployments/managing-workflow-runs/approving-workflow-runs-from-public-forks).
+1. Under **Approval for running fork pull request workflows from contributors**, choose which subset of users will require approval before running workflows on their pull requests. Both the pull request author and the actor of the pull request event triggering the workflow will be checked to determine if approval is required. If approval is required, a user with write access to the repository must approve the pull request workflow to be run. See [AUTOTITLE](/actions/how-tos/manage-workflow-runs/approve-runs-from-forks).
 
    >[!WARNING] When requiring approvals only for first-time contributors (the first two settings), a user that has had any commit or pull request merged into the repository will not require approval. A malicious user could meet this requirement by getting a simple typo or other innocuous change accepted by a maintainer, either as part of a pull request they have authored or as part of another user's pull request.
 
diff --git a/data/reusables/actions/workflows/run-on-specific-branches-or-tags1.md b/data/reusables/actions/workflows/run-on-specific-branches-or-tags1.md
@@ -5,6 +5,6 @@ Use the `branches` filter when you want to include branch name patterns or when
 
 Use the `tags` filter when you want to include tag name patterns or when you want to both include and exclude tag names patterns. Use the `tags-ignore` filter when you only want to exclude tag name patterns. You cannot use both the `tags` and `tags-ignore` filters for the same event in a workflow.
 
-If you define only `tags`/`tags-ignore` or only `branches`/`branches-ignore`, the workflow won't run for events affecting the undefined Git ref. If you define neither `tags`/`tags-ignore` or `branches`/`branches-ignore`, the workflow will run for events affecting either branches or tags. If you define both `branches`/`branches-ignore` and [`paths`/`paths-ignore`](/actions/using-workflows/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore), the workflow will only run when both filters are satisfied.
+If you define only `tags`/`tags-ignore` or only `branches`/`branches-ignore`, the workflow won't run for events affecting the undefined Git ref. If you define neither `tags`/`tags-ignore` or `branches`/`branches-ignore`, the workflow will run for events affecting either branches or tags. If you define both `branches`/`branches-ignore` and [`paths`/`paths-ignore`](/actions/reference/workflows-and-actions/workflow-syntax#onpushpull_requestpull_request_targetpathspaths-ignore), the workflow will only run when both filters are satisfied.
 
-The `branches`, `branches-ignore`, `tags`, and `tags-ignore` keywords accept glob patterns that use characters like `*`, `**`, `+`, `?`, `!` and others to match more than one branch or tag name. If a name contains any of these characters and you want a literal match, you need to _escape_ each of these special characters with `\`. For more information about glob patterns, see the [AUTOTITLE](/actions/using-workflows/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet).
+The `branches`, `branches-ignore`, `tags`, and `tags-ignore` keywords accept glob patterns that use characters like `*`, `**`, `+`, `?`, `!` and others to match more than one branch or tag name. If a name contains any of these characters and you want a literal match, you need to _escape_ each of these special characters with `\`. For more information about glob patterns, see the [AUTOTITLE](/actions/reference/workflows-and-actions/workflow-syntax#filter-pattern-cheat-sheet).
diff --git a/data/reusables/actions/workflows/section-specifying-branches.md b/data/reusables/actions/workflows/section-specifying-branches.md
@@ -1,7 +1,7 @@
 
 When using the `workflow_run` event, you can specify what branches the triggering workflow must run on in order to trigger your workflow.
 
-The `branches` and `branches-ignore` filters accept glob patterns that use characters like `*`, `**`, `+`, `?`, `!` and others to match more than one branch name. If a name contains any of these characters and you want a literal match, you need to _escape_ each of these special characters with `\`. For more information about glob patterns, see the [AUTOTITLE](/actions/using-workflows/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet).
+The `branches` and `branches-ignore` filters accept glob patterns that use characters like `*`, `**`, `+`, `?`, `!` and others to match more than one branch name. If a name contains any of these characters and you want a literal match, you need to _escape_ each of these special characters with `\`. For more information about glob patterns, see the [AUTOTITLE](/actions/reference/workflows-and-actions/workflow-syntax#filter-pattern-cheat-sheet).
 
 For example, a workflow with the following trigger will only run when the workflow named `Build` runs on a branch whose name starts with `releases/`:
 
diff --git a/data/reusables/actions/workflows/section-triggering-a-workflow-types.md b/data/reusables/actions/workflows/section-triggering-a-workflow-types.md
@@ -1,6 +1,6 @@
 Use `on.<event_name>.types` to define the type of activity that will trigger a workflow run. Most GitHub events are triggered by more than one type of activity. For example, the `label` is triggered when a label is `created`, `edited`, or `deleted`. The `types` keyword enables you to narrow down activity that causes the workflow to run. When only one activity type triggers a webhook event, the `types` keyword is unnecessary.
 
-You can use an array of event `types`. For more information about each event and their activity types, see [AUTOTITLE](/actions/using-workflows/events-that-trigger-workflows#available-events).
+You can use an array of event `types`. For more information about each event and their activity types, see [AUTOTITLE](/actions/reference/workflows-and-actions/events-that-trigger-workflows#available-events).
 
 ```yaml
 on:
diff --git a/data/reusables/actions/workflows/section-triggering-a-workflow.md b/data/reusables/actions/workflows/section-triggering-a-workflow.md
@@ -1,5 +1,5 @@
 
-To automatically trigger a workflow, use `on` to define which events can cause the workflow to run. For a list of available events, see [AUTOTITLE](/actions/using-workflows/events-that-trigger-workflows).
+To automatically trigger a workflow, use `on` to define which events can cause the workflow to run. For a list of available events, see [AUTOTITLE](/actions/reference/workflows-and-actions/events-that-trigger-workflows).
 
 You can define single or multiple events that can trigger a workflow, or set a time schedule. You can also restrict the execution of a workflow to only occur for specific files, tags, or branch changes. These options are described in the following sections.
 
diff --git a/data/reusables/actions/workflows/triggering-a-workflow-paths1.md b/data/reusables/actions/workflows/triggering-a-workflow-paths1.md
@@ -10,4 +10,4 @@ Use the `paths` filter when you want to include file path patterns or when you w
 
 If you define both `branches`/`branches-ignore` and `paths`/`paths-ignore`, the workflow will only run when both filters are satisfied.
 
-The `paths` and `paths-ignore` keywords accept glob patterns that use the `*` and `**` wildcard characters to match more than one path name. For more information, see the [AUTOTITLE](/actions/using-workflows/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet).
+The `paths` and `paths-ignore` keywords accept glob patterns that use the `*` and `**` wildcard characters to match more than one path name. For more information, see the [AUTOTITLE](/actions/reference/workflows-and-actions/workflow-syntax#filter-pattern-cheat-sheet).
diff --git a/data/reusables/actions/workflows/triggering-a-workflow-paths2.md b/data/reusables/actions/workflows/triggering-a-workflow-paths2.md
@@ -9,4 +9,4 @@ on:
 
 {% data reusables.pull_requests.path-filtering-required-workflows %}
 
-If a workflow is skipped due to path filtering, [branch filtering](/actions/using-workflows/workflow-syntax-for-github-actions#onpull_requestpull_request_targetbranchesbranches-ignore), or a [commit message](/actions/managing-workflow-runs/skipping-workflow-runs), then checks associated with that workflow will remain in a "Pending" state. A pull request that requires those checks to be successful will be blocked from merging.
+If a workflow is skipped due to path filtering, [branch filtering](/actions/reference/workflows-and-actions/workflow-syntax#onpull_requestpull_request_targetbranchesbranches-ignore), or a [commit message](/actions/how-tos/manage-workflow-runs/skip-workflow-runs), then checks associated with that workflow will remain in a "Pending" state. A pull request that requires those checks to be successful will be blocked from merging.
diff --git a/data/reusables/actions/workflows/triggering-workflow-branches1.md b/data/reusables/actions/workflows/triggering-workflow-branches1.md
@@ -2,6 +2,6 @@ When using the `pull_request` and `pull_request_target` events, you can configur
 
 Use the `branches` filter when you want to include branch name patterns or when you want to both include and exclude branch names patterns. Use the `branches-ignore` filter when you only want to exclude branch name patterns. You cannot use both the `branches` and `branches-ignore` filters for the same event in a workflow.
 
-If you define both `branches`/`branches-ignore` and [`paths`/`paths-ignore`](/actions/using-workflows/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore), the workflow will only run when both filters are satisfied.
+If you define both `branches`/`branches-ignore` and [`paths`/`paths-ignore`](/actions/reference/workflows-and-actions/workflow-syntax#onpushpull_requestpull_request_targetpathspaths-ignore), the workflow will only run when both filters are satisfied.
 
-The `branches` and `branches-ignore` keywords accept glob patterns that use characters like `*`, `**`, `+`, `?`, `!` and others to match more than one branch name. If a name contains any of these characters and you want a literal match, you need to escape each of these special characters with `\`. For more information about glob patterns, see the [AUTOTITLE](/actions/using-workflows/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet).
+The `branches` and `branches-ignore` keywords accept glob patterns that use characters like `*`, `**`, `+`, `?`, `!` and others to match more than one branch name. If a name contains any of these characters and you want a literal match, you need to escape each of these special characters with `\`. For more information about glob patterns, see the [AUTOTITLE](/actions/reference/workflows-and-actions/workflow-syntax#filter-pattern-cheat-sheet).
diff --git a/data/reusables/actions/workflows/triggering-workflow-branches2.md b/data/reusables/actions/workflows/triggering-workflow-branches2.md

Original file line number	Diff line number	Diff line change
`@@ -1,3 +1,3 @@`
`1`		-The triggered workflow receives the inputs in the `inputs` context. For more information, see [Contexts](/actions/learn-github-actions/contexts#inputs-context).
	`1`	+The triggered workflow receives the inputs in the `inputs` context. For more information, see [Contexts](/actions/reference/workflows-and-actions/contexts#inputs-context).
`2`	`2`
`3`	`3`	`{% data reusables.actions.inputs-vs-github-event-inputs %}`
Original file line number	Diff line number	Diff line change
`@@ -1 +1 @@`
`1`		-You can set the default permissions granted to the `GITHUB_TOKEN`. For more information about the `GITHUB_TOKEN`, see [AUTOTITLE](/actions/security-guides/automatic-token-authentication). You can choose a restricted set of permissions as the default, or apply permissive settings.
	`1`	+You can set the default permissions granted to the `GITHUB_TOKEN`. For more information about the `GITHUB_TOKEN`, see [AUTOTITLE](/actions/tutorials/authenticate-with-github_token). You can choose a restricted set of permissions as the default, or apply permissive settings.
Original file line number	Diff line number	Diff line change
`@@ -1 +1 @@`
`1`		-Anyone with write access to a repository can modify the permissions granted to the `GITHUB_TOKEN`, adding or removing access as required, by editing the `permissions` key in the workflow file. For more information, see [`permissions`](/actions/using-workflows/workflow-syntax-for-github-actions#permissions).
	`1`	+Anyone with write access to a repository can modify the permissions granted to the `GITHUB_TOKEN`, adding or removing access as required, by editing the `permissions` key in the workflow file. For more information, see [`permissions`](/actions/reference/workflows-and-actions/workflow-syntax#permissions).
Original file line number	Diff line number	Diff line change
`@@ -1 +1 @@`
`1`		`-For more information about approving workflow runs that this policy applies to, see [AUTOTITLE](/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks).`
	`1`	`+For more information about approving workflow runs that this policy applies to, see [AUTOTITLE](/actions/how-tos/manage-workflow-runs/approve-runs-from-forks).`
Original file line number	Diff line number	Diff line change
`@@ -1 +1 @@`
`1`		-Workflow runs triggered by {% data variables.product.prodname_dependabot %} pull requests run as if they are from a forked repository, and therefore use a read-only `GITHUB_TOKEN`. These workflow runs cannot access any secrets. For information about strategies to keep these workflows secure, see [AUTOTITLE](/actions/security-guides/security-hardening-for-github-actions).
	`1`	+Workflow runs triggered by {% data variables.product.prodname_dependabot %} pull requests run as if they are from a forked repository, and therefore use a read-only `GITHUB_TOKEN`. These workflow runs cannot access any secrets. For information about strategies to keep these workflows secure, see [AUTOTITLE](/actions/reference/security/secure-use).
Original file line number	Diff line number	Diff line change
`@@ -1 +1 @@`
`1`		`-To get started with preconfigured workflows, browse through the list of templates in the [actions/starter-workflows](https://github.com/actions/starter-workflows) repository. For more information, see [AUTOTITLE](/actions/writing-workflows/using-starter-workflows).`
	`1`	`+To get started with preconfigured workflows, browse through the list of templates in the [actions/starter-workflows](https://github.com/actions/starter-workflows) repository. For more information, see [AUTOTITLE](/actions/how-tos/write-workflows/use-workflow-templates).`