Update redirected internal links in packages (#62116)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: heiskr

content/packages/learn-github-packages/about-permissions-for-github-packages.md

@@ -84,7 +84,7 @@ When you create a {% data variables.product.prodname_actions %} workflow, you ca
 For more information, see:{% ifversion fpt or ghec %}
 * [AUTOTITLE](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility){% endif %}
 * [AUTOTITLE](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions)
-* [AUTOTITLE](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)
+* [AUTOTITLE](/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens)
 * [AUTOTITLE](/apps/oauth-apps/building-oauth-apps/scopes-for-oauth-apps#available-scopes)
 
 ## About repository transfers
@@ -109,7 +109,7 @@ For more conceptual background on {% data variables.product.prodname_actions %}
 * To publish, install, delete, and restore packages associated with the workflow repository, use `GITHUB_TOKEN`.
 * To install packages associated with other private repositories that `GITHUB_TOKEN` can't access, use a {% data variables.product.pat_v1 %}
 
-For more information about `GITHUB_TOKEN` used in {% data variables.product.prodname_actions %} workflows, see [AUTOTITLE](/actions/security-guides/automatic-token-authentication#using-the-github_token-in-a-workflow).
+For more information about `GITHUB_TOKEN` used in {% data variables.product.prodname_actions %} workflows, see [AUTOTITLE](/actions/tutorials/authenticate-with-github_token#using-the-github_token-in-a-workflow).
 
 {% ifversion fpt or ghec %}
 

content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md

@@ -124,7 +124,7 @@ Granting a repository access here also allows {% data variables.product.prodname
 
 > [!NOTE]
 > * Syncing your package with a repository {% data variables.package_registry.package-settings-actions-access-menu %} is different than connecting your package to a repository. For more information about linking a repository to your package, see [AUTOTITLE](/packages/learn-github-packages/connecting-a-repository-to-a-package).
-> * You can choose to limit permissions to workflow jobs usings the `permissions` key and `packages` scope. For more information, see [AUTOTITLE](/actions/using-jobs/assigning-permissions-to-jobs).
+> * You can choose to limit permissions to workflow jobs using the `permissions` key and `packages` scope. For more information, see [AUTOTITLE](/actions/tutorials/authenticate-with-github_token#modifying-the-permissions-for-the-githubtoken).
 > * {% data reusables.package_registry.public-forks-private-packages %}
 
 ### {% data variables.product.prodname_actions %} access for packages scoped to personal accounts

content/packages/learn-github-packages/introduction-to-github-packages.md

@@ -33,7 +33,7 @@ You can view a package's README, as well as metadata such as licensing, download
 
 {% ifversion ghes %}
 
-For more information about the configuration of {% data variables.product.prodname_registry %} on {% data variables.product.prodname_ghe_server %}, see [AUTOTITLE](/admin/packages/getting-started-with-github-packages-for-your-enterprise).
+For more information about the configuration of {% data variables.product.prodname_registry %} on {% data variables.product.prodname_ghe_server %}, see [AUTOTITLE](/admin/configuring-packages/getting-started-with-github-packages-for-your-enterprise).
 
 {% endif %}
 
@@ -72,7 +72,7 @@ For more information, see [AUTOTITLE](/code-security/concepts/supply-chain-secur
 
 {% data reusables.billing.default-over-quota-behavior %}
 
-For more information, see [AUTOTITLE](/billing/managing-billing-for-github-packages/about-billing-for-github-packages).
+For more information, see [AUTOTITLE](/billing/concepts/product-billing/github-packages).
 
 {% endif %}
 
@@ -95,7 +95,7 @@ For more information, see [AUTOTITLE](/billing/managing-billing-for-github-packa
 {% ifversion ghes %}
 
 > [!NOTE]
-> When enabling the Docker registry, we highly recommend also enabling subdomain isolation. For more information, see [AUTOTITLE](/admin/configuration/configuring-network-settings/enabling-subdomain-isolation).
+> When enabling the Docker registry, we highly recommend also enabling subdomain isolation. For more information, see [AUTOTITLE](/admin/configuring-settings/hardening-security-for-your-enterprise/enabling-subdomain-isolation).
 
 {% endif %}
 
@@ -126,7 +126,7 @@ When you use the GraphQL API to query and delete private packages, you must use
 
 For more information, see {% ifversion ghes %}[AUTOTITLE](/packages/learn-github-packages/deleting-and-restoring-a-package) and {% endif %}[AUTOTITLE](/graphql/guides/forming-calls-with-graphql).
 
-You can configure webhooks to subscribe to package-related events, such as when a package is published or updated. For more information, see the [AUTOTITLE](/webhooks-and-events/webhooks/webhook-events-and-payloads#package).
+You can configure webhooks to subscribe to package-related events, such as when a package is published or updated. For more information, see the [AUTOTITLE](/webhooks/webhook-events-and-payloads#package).
 
 ## Contacting support
 

content/packages/learn-github-packages/publishing-a-package.md

@@ -23,7 +23,7 @@ You can help people understand and use your package by providing a description a
 {% data reusables.package_registry.public-or-private-packages %} A repository can be connected to more than one package. To prevent confusion, make sure the README and description clearly provide information about each package.
 
 {% ifversion fpt or ghec %}
-If a new version of a package fixes a security vulnerability, you should publish a security advisory in your repository. {% data variables.product.prodname_dotcom %} reviews each published security advisory and may use it to send {% data variables.product.prodname_dependabot_alerts %} to affected repositories. For more information, see [AUTOTITLE](/code-security/security-advisories/working-with-repository-security-advisories/about-repository-security-advisories).
+If a new version of a package fixes a security vulnerability, you should publish a security advisory in your repository. {% data variables.product.prodname_dotcom %} reviews each published security advisory and may use it to send {% data variables.product.prodname_dependabot_alerts %} to affected repositories. For more information, see [AUTOTITLE](/code-security/concepts/vulnerability-reporting-and-management/repository-security-advisories).
 {% endif %}
 
 ## Publishing a package

content/packages/managing-github-packages-using-github-actions-workflows/example-workflows-for-publishing-a-package.md

@@ -14,7 +14,7 @@ category:
 
 You can find example workflows in [AUTOTITLE](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions) or in any of these {% data variables.product.prodname_actions %} guides:
 
-* [Publishing Node.js packages](/actions/publishing-packages/publishing-nodejs-packages)
-* [Publishing Docker images](/actions/publishing-packages/publishing-docker-images)
-* [Publishing Java packages with Maven](/actions/publishing-packages/publishing-java-packages-with-maven)
-* [Publishing Java packages with Gradle](/actions/publishing-packages/publishing-java-packages-with-gradle)
+* [Publishing Node.js packages](/actions/tutorials/publish-packages/publish-nodejs-packages)
+* [Publishing Docker images](/actions/tutorials/publish-packages/publish-docker-images)
+* [Publishing Java packages with Maven](/actions/tutorials/publish-packages/publish-java-packages-with-maven)
+* [Publishing Java packages with Gradle](/actions/tutorials/publish-packages/publish-java-packages-with-gradle)

content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md

@@ -22,7 +22,7 @@ category:
 
 ## About {% data variables.product.prodname_registry %} with {% data variables.product.prodname_actions %}
 
-{% data reusables.repositories.about-github-actions %} {% data reusables.repositories.actions-ci-cd %} For more information, see [AUTOTITLE](/actions/learn-github-actions).
+{% data reusables.repositories.about-github-actions %} {% data reusables.repositories.actions-ci-cd %} For more information, see [AUTOTITLE](/actions/how-tos/write-workflows).
 
 You can extend the CI and CD capabilities of your repository by publishing or installing packages as part of your workflow.
 
@@ -36,21 +36,21 @@ Some {% data variables.product.prodname_registry %} registries support granular
 
 Some {% data variables.product.prodname_registry %} registries only support repository-scoped permissions, and do not support granular permissions. For a list of these registries, see [AUTOTITLE](/packages/learn-github-packages/about-permissions-for-github-packages#permissions-for-repository-scoped-packages).
 
-If you want your workflow to access a {% data variables.product.prodname_registry %} registry that does not support granular permissions, then we recommend using the `GITHUB_TOKEN` that {% data variables.product.github %} automatically creates for your repository when you enable {% data variables.product.prodname_actions %}. You should set the permissions for this access token in the workflow file to grant read access for the `contents` scope and write access for the `packages` scope. For forks, the `GITHUB_TOKEN` is granted read access for the parent repository. For more information, see [AUTOTITLE](/actions/security-guides/automatic-token-authentication).
+If you want your workflow to access a {% data variables.product.prodname_registry %} registry that does not support granular permissions, then we recommend using the `GITHUB_TOKEN` that {% data variables.product.github %} automatically creates for your repository when you enable {% data variables.product.prodname_actions %}. You should set the permissions for this access token in the workflow file to grant read access for the `contents` scope and write access for the `packages` scope. For forks, the `GITHUB_TOKEN` is granted read access for the parent repository. For more information, see [AUTOTITLE](/actions/tutorials/authenticate-with-github_token).
 
-You can reference the `GITHUB_TOKEN` in your workflow file using the {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %} context. For more information, see [AUTOTITLE](/actions/security-guides/automatic-token-authentication).
+You can reference the `GITHUB_TOKEN` in your workflow file using the {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %} context. For more information, see [AUTOTITLE](/actions/tutorials/authenticate-with-github_token).
 
 ## About permissions and package access
 
 ### Packages scoped to users or organizations
 
 Registries that support granular permissions allow users to create and administer packages as free-standing resources at the organization level. Packages can be scoped to an organization or personal account and you can customize access to each of your packages separately from repository permissions.
 
-All workflows accessing registries that support granular permissions should use the `GITHUB_TOKEN` instead of a {% data variables.product.pat_generic %}. For more information about security best practices, see [AUTOTITLE](/actions/security-guides/security-hardening-for-github-actions#using-secrets).
+All workflows accessing registries that support granular permissions should use the `GITHUB_TOKEN` instead of a {% data variables.product.pat_generic %}. For more information about security best practices, see [AUTOTITLE](/actions/reference/security/secure-use#use-secrets-for-sensitive-information).
 
 ### Packages scoped to repositories
 
-When you enable GitHub Actions, GitHub installs a GitHub App on your repository. The `GITHUB_TOKEN` secret is a GitHub App installation access token. You can use the installation access token to authenticate on behalf of the GitHub App installed on your repository. The token's permissions are limited to the repository that contains your workflow. For more information, see [AUTOTITLE](/actions/security-guides/automatic-token-authentication#about-the-github_token-secret).
+When you enable GitHub Actions, GitHub installs a GitHub App on your repository. The `GITHUB_TOKEN` secret is a GitHub App installation access token. You can use the installation access token to authenticate on behalf of the GitHub App installed on your repository. The token's permissions are limited to the repository that contains your workflow. For more information, see [AUTOTITLE](/actions/tutorials/authenticate-with-github_token#about-the-github_token-secret).
 
 {% data variables.product.prodname_registry %} allows you to push and pull packages through the `GITHUB_TOKEN` available to a {% data variables.product.prodname_actions %} workflow.
 
@@ -78,7 +78,7 @@ You can use {% data variables.product.prodname_actions %} to automatically publi
 
 {% data reusables.package_registry.actions-configuration %}
 
-The following example demonstrates how you can use {% data variables.product.prodname_actions %} to build {% ifversion not fpt or ghec %}and test{% endif %} your app, and then automatically create a Docker image and publish it to {% data variables.product.prodname_registry %}. The relevant settings are explained in the code. For full details about each element in a workflow, see [AUTOTITLE](/actions/using-workflows/workflow-syntax-for-github-actions).
+The following example demonstrates how you can use {% data variables.product.prodname_actions %} to build {% ifversion not fpt or ghec %}and test{% endif %} your app, and then automatically create a Docker image and publish it to {% data variables.product.prodname_registry %}. The relevant settings are explained in the code. For full details about each element in a workflow, see [AUTOTITLE](/actions/reference/workflows-and-actions/workflow-syntax).
 
 Create a new workflow file in your repository (such as `.github/workflows/deploy-image.yml`), and add the following YAML.
 
@@ -180,17 +180,17 @@ A few minutes after the workflow has completed, the new package will be visible
 
 You can install packages as part of your CI flow using {% data variables.product.prodname_actions %}. For example, you could configure a workflow so that anytime a developer pushes code to a pull request, the workflow resolves dependencies by downloading and installing packages hosted by {% data variables.product.prodname_registry %}. Then, the workflow can run CI tests that require the dependencies.
 
-Installing packages hosted by {% data variables.product.prodname_registry %} through {% data variables.product.prodname_actions %} requires minimal configuration or additional authentication when you use the `GITHUB_TOKEN`.{% ifversion fpt or ghec %} Data transfer is also free when an action installs a package. For more information, see [AUTOTITLE](/billing/managing-billing-for-github-packages/about-billing-for-github-packages).{% endif %}
+Installing packages hosted by {% data variables.product.prodname_registry %} through {% data variables.product.prodname_actions %} requires minimal configuration or additional authentication when you use the `GITHUB_TOKEN`.{% ifversion fpt or ghec %} Data transfer is also free when an action installs a package. For more information, see [AUTOTITLE](/billing/concepts/product-billing/github-packages).{% endif %}
 
 {% data reusables.package_registry.actions-configuration %}
 
 ## Upgrading a workflow that accesses a registry using a {% data variables.product.pat_generic %}
 
 {% data variables.product.prodname_registry %} supports the `GITHUB_TOKEN` for easy and secure authentication in your workflows. If you're using a registry that supports granular permissions, and your workflow is using a {% data variables.product.pat_generic %} to authenticate to the registry, then we highly recommend you update your workflow to use the `GITHUB_TOKEN`.
 
-For more information about the `GITHUB_TOKEN`, see [AUTOTITLE](/actions/security-guides/automatic-token-authentication#using-the-github_token-in-a-workflow).
+For more information about the `GITHUB_TOKEN`, see [AUTOTITLE](/actions/tutorials/authenticate-with-github_token#using-the-github_token-in-a-workflow).
 
-Using the `GITHUB_TOKEN`, instead of a {% data variables.product.pat_v1 %} with the `repo` scope, increases the security of your repository as you don't need to use a long-lived {% data variables.product.pat_generic %} that offers unnecessary access to the repository where your workflow is run. For more information about security best practices, see [AUTOTITLE](/actions/security-guides/security-hardening-for-github-actions#using-secrets).
+Using the `GITHUB_TOKEN`, instead of a {% data variables.product.pat_v1 %} with the `repo` scope, increases the security of your repository as you don't need to use a long-lived {% data variables.product.pat_generic %} that offers unnecessary access to the repository where your workflow is run. For more information about security best practices, see [AUTOTITLE](/actions/reference/security/secure-use#use-secrets-for-sensitive-information).
 
 1. Navigate to your package landing page.
 {% data reusables.package_registry.package-settings-actions-access %}

content/packages/quickstart.md

@@ -125,7 +125,7 @@ If you use a {% data variables.enterprise.prodname_managed_user %}, you cannot p
 
 1. The workflow that you created will run whenever a new release is created in your repository. If the tests pass, then the package will be published to {% data variables.product.prodname_registry %}.
 
-    To test this out, navigate to the **Code** tab in your repository and create a new release. For more information, see [Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository#creating-a-release).
+    To test this out, navigate to the **Code** tab in your repository and create a new release. For more information, see [Managing releases in a repository](/repositories/releasing-projects-on-github/managing-releases-in-a-repository#creating-a-release).
 
 ## Viewing your published package
 
@@ -146,5 +146,5 @@ The basic workflow you just added runs any time a new release is created in your
 Combining {% data variables.product.prodname_registry %} and {% data variables.product.prodname_actions %} can help you automate nearly every aspect of your application development processes. Ready to get started? Here are some helpful resources for taking your next steps with {% data variables.product.prodname_registry %} and {% data variables.product.prodname_actions %}:
 
 * [AUTOTITLE](/packages/learn-github-packages) for an in-depth tutorial on GitHub Packages
-* [AUTOTITLE](/actions/learn-github-actions) for an in-depth tutorial on GitHub Actions
+* [AUTOTITLE](/actions/how-tos/write-workflows) for an in-depth tutorial on GitHub Actions
 * [AUTOTITLE](/packages/working-with-a-github-packages-registry) for specific uses cases and examples

content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md

@@ -28,7 +28,7 @@ category:
 {% ifversion ghes %}
 
 > [!NOTE]
-> {% data reusables.package_registry.container-registry-ghes-migration-availability %} For more information about finding the version of {% data variables.product.prodname_ghe_server %} that you use, see [AUTOTITLE](/get-started/learning-about-github/about-versions-of-github-docs#github-enterprise-server).
+> {% data reusables.package_registry.container-registry-ghes-migration-availability %} For more information about finding the version of {% data variables.product.prodname_ghe_server %} that you use, see [AUTOTITLE](/get-started/using-github-docs/about-versions-of-github-docs#github-enterprise-server).
 
 {% endif %}
 
@@ -45,12 +45,12 @@ After migration, you'll no longer be able to use the GraphQL API to query for pa
 
 ## About billing for {% data variables.product.prodname_container_registry %}
 
-For more information about billing for the {% data variables.product.prodname_container_registry %}, see [AUTOTITLE](/billing/managing-billing-for-github-packages/about-billing-for-github-packages).
+For more information about billing for the {% data variables.product.prodname_container_registry %}, see [AUTOTITLE](/billing/concepts/product-billing/github-packages).
 
 {% else %}
 
 ## Further reading
 
-* [AUTOTITLE](/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry)
+* [AUTOTITLE](/admin/configuring-packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry)
 
 {% endif %}