Merge pull request #45582 from github/repo-sync

Repo sync

Author: docs-bot

content/account-and-profile/how-tos/contribution-settings/troubleshooting-missing-contributions.md

@@ -58,15 +58,15 @@ Generic email addresses, such as `jane@computer.local`, cannot be added to {% da
 Commits are only counted if they are made in the default branch or the `gh-pages` branch (for repositories with project sites). For more information, see [AUTOTITLE](/pages/getting-started-with-github-pages/what-is-github-pages#types-of-github-pages-sites).
 
 If your commits are in a non-default or non-`gh-pages` branch and you'd like them to count toward your contributions, you will need to do one of the following:
-* [Open a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request) to have your changes merged into the default branch or the `gh-pages` branch.
+* [Open a pull request](/pull-requests/how-tos/create-pull-requests/creating-a-pull-request) to have your changes merged into the default branch or the `gh-pages` branch.
 * [Change the default branch](/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch) of the repository.
 
 > [!WARNING]
 > Changing the default branch of the repository will change it for all repository collaborators. Only do this if you want the new branch to become the base against which all future pull requests and commits will be made.
 
 ## Commit was made in a fork
 
-Commits made in a fork will not count toward your contributions. To make them count, you must open a pull request to have your changes merged into the parent repository. For more information, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request).
+Commits made in a fork will not count toward your contributions. To make them count, you must open a pull request to have your changes merged into the parent repository. For more information, see [AUTOTITLE](/pull-requests/how-tos/create-pull-requests/creating-a-pull-request).
 
 ## Next steps
 

content/account-and-profile/how-tos/email-preferences/troubleshooting-email-verification.md

@@ -23,8 +23,8 @@ category:
 
 If your account is restricted and you're told to change the email address on your account before access can be restored, you must update your account email and then ask {% data variables.contact.github_support %} to review the restriction.
 
-1. Add a different, non-disposable email address and set it as your primary email address. For more information, see [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/changing-your-primary-email-address).
-1. Verify your new primary email address. For more information, see [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/verifying-your-email-address).
+1. Add a different, non-disposable email address and set it as your primary email address. For more information, see [AUTOTITLE](/account-and-profile/how-tos/email-preferences/changing-your-primary-email-address).
+1. Verify your new primary email address. For more information, see [AUTOTITLE](/account-and-profile/how-tos/email-preferences/verifying-your-email-address).
 1. Remove the previous email address from your account.
 1. Contact {% data variables.contact.github_support %} and ask for a review of the restriction.
 

content/actions/get-started/quickstart.md

@@ -38,7 +38,7 @@ For an overview of {% data variables.product.prodname_actions %} workflows, see
 ## Prerequisites
 
 This guide assumes that:
-* You have at least a basic knowledge of how to use {% data variables.product.prodname_dotcom %}. If you don't, you'll find it helpful to read some of the articles in the documentation for repositories and pull requests first. For example, see [AUTOTITLE](/repositories/creating-and-managing-repositories/quickstart-for-repositories), [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches), and [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests).
+* You have at least a basic knowledge of how to use {% data variables.product.prodname_dotcom %}. If you don't, you'll find it helpful to read some of the articles in the documentation for repositories and pull requests first. For example, see [AUTOTITLE](/repositories/creating-and-managing-repositories/quickstart-for-repositories), [AUTOTITLE](/pull-requests/reference/branches), and [AUTOTITLE](/pull-requests/reference/pull-requests).
 * You have a repository on {% data variables.product.github %} where you can add files.
 * You have access to {% data variables.product.prodname_actions %}.
 

content/actions/how-tos/deploy/configure-and-manage-deployments/view-deployment-history.md

@@ -37,7 +37,7 @@ By default, the deployments page shows currently active deployments from select
    * **To view recent deployments for a specific environment**, in the "Environments" section of the left sidebar, click an environment.
    * **To pin an environment to the top of the deployment history list**, repository administrators can click {% octicon "pin" aria-label="Pin environment" %} to the right of the environment. You can pin up to ten environments.
    * **To view the commit that triggered a deployment**, in the deployment history list, click the commit message for the deployment you want to view.
-      >[!NOTE]Deployments from commits that originate from a fork outside of the repository will not show links to the source pull request and branch related to each deployment. For more information about forks, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks).
+      >[!NOTE]Deployments from commits that originate from a fork outside of the repository will not show links to the source pull request and branch related to each deployment. For more information about forks, see [AUTOTITLE](/pull-requests/reference/forks).
    * **To view the URL for a deployment**, to the right of the commit message in the deployment history list, click {% octicon "link-external" aria-label="Navigate to deployment URL" %}.
    * **To navigate to the workflow run logs associated with a deployment**, to the right of the commit message in the deployment history list, click {% octicon "kebab-horizontal" aria-label="View logs" %}, then click **View logs**.
 1. Optionally, to filter the deployment history list, create a filter.

content/apps/creating-github-apps/writing-code-for-a-github-app/building-a-github-app-that-responds-to-webhook-events.md

@@ -319,7 +319,7 @@ For testing, you will use your computer or codespace as a server. Your app will
 
 Now that your server is running and receiving forwarded webhooks events, test your app by opening a pull request on the repository that you selected when you installed your app.
 
-1. Open a pull request on the repository that you selected when you installed your app. For more information, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request).
+1. Open a pull request on the repository that you selected when you installed your app. For more information, see [AUTOTITLE](/pull-requests/how-tos/create-pull-requests/creating-a-pull-request).
 
    Make sure to use the repository that you selected when you installed your app, not the repository where your app's code is stored. For more information, see [Install your app](#install-your-app).
 

content/apps/creating-github-apps/writing-code-for-a-github-app/quickstart.md

@@ -132,7 +132,7 @@ For testing, you will use your computer or codespace as a server. Your app will
 
 Now that your server is running and receiving forwarded webhooks events, test your app by opening a pull request.
 
-1. Open a pull request on the repository you created in [Step 5: Install your app](#step-5-install-your-app). For more information, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request).
+1. Open a pull request on the repository you created in [Step 5: Install your app](#step-5-install-your-app). For more information, see [AUTOTITLE](/pull-requests/how-tos/create-pull-requests/creating-a-pull-request).
 1. Navigate to your webhook proxy URL on smee.io. You should see a `pull_request` event. This indicates that {% data variables.product.company_short %} successfully sent a pull request event when you created a pull request.
 1. In the terminal where you ran `npm run server`, you should see something like "Received a pull request event for #1" where the integer after the `#` is the number of the pull request that you opened.
 1. In the timeline of your pull request, you should see a comment from your app. The comment uses the contents of the `message.md` file in your cloned repository.

content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md

@@ -23,7 +23,7 @@ To keep your account secure, we recommend you follow these best practices:
 * Generate a unique password for {% data variables.product.github %}. If you use your {% data variables.product.github %} password elsewhere and that service is compromised, then attackers or other malicious actors could use that information to access your account.
 * Configure two-factor authentication for your personal account. For more information, see [AUTOTITLE](/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication).
 * {% data reusables.passkeys.add-passkey-option %}
-* Never share your password, even with a potential collaborator. Each person should use their own personal account on {% data variables.product.github %}. For more information on ways to collaborate, see: [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/repository-access-and-collaboration/inviting-collaborators-to-a-personal-repository), [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models), or [AUTOTITLE](/organizations/collaborating-with-groups-in-organizations).
+* Never share your password, even with a potential collaborator. Each person should use their own personal account on {% data variables.product.github %}. For more information on ways to collaborate, see: [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/repository-access-and-collaboration/inviting-collaborators-to-a-personal-repository), [AUTOTITLE](/pull-requests/reference/pull-requests), or [AUTOTITLE](/organizations/collaborating-with-groups-in-organizations).
 
 {% data reusables.repositories.blocked-passwords %}
 

content/billing/how-tos/manage-for-client/create-as-csp-partner.md

@@ -21,7 +21,7 @@ Before you start, make sure you know:
 * Enterprise name your client would like to use
 * Email address for receipts
 * Number of seats your client needs in the enterprise
-* Enterprise account type required by your client, see [AUTOTITLE](/enterprise-onboarding/getting-started-with-your-enterprise/choose-an-enterprise-type)
+* Enterprise account type required by your client, see [AUTOTITLE](/admin/concepts/enterprise-fundamentals/choose-an-enterprise-type)
 
 ## Step 1: Create the enterprise account in the Azure portal
 
@@ -30,7 +30,7 @@ As a Microsoft CSP partner, you can get started with {% data variables.product.p
 1. Sign in to the Microsoft Azure portal.
 1. In the search bar, type "{% data variables.product.prodname_dotcom %}" and select **{% data variables.product.prodname_dotcom %}** to go the landing page.
 1. Select **Get started with {% data variables.product.prodname_enterprise %}**.
-1. Choose an enterprise type. To help you decide which choice is best for the enterprise, see [AUTOTITLE](/enterprise-onboarding/getting-started-with-your-enterprise/choose-an-enterprise-type).
+1. Choose an enterprise type. To help you decide which choice is best for the enterprise, see [AUTOTITLE](/admin/concepts/enterprise-fundamentals/choose-an-enterprise-type).
 1. Complete the form with your client's information.
 {% data reusables.billing.enterprise-create-button %}
 

content/billing/how-tos/manage-for-client/create-client-enterprise.md

@@ -21,7 +21,7 @@ Before you start, make sure you know:
 * Enterprise name your client would like to use
 * Email address for receipts
 * Number of seats your client needs in the enterprise
-* Enterprise account type required by your client, see [AUTOTITLE](/enterprise-onboarding/getting-started-with-your-enterprise/choose-an-enterprise-type)
+* Enterprise account type required by your client, see [AUTOTITLE](/admin/concepts/enterprise-fundamentals/choose-an-enterprise-type)
 
 ## Step 1: Create your personal account on {% data variables.product.prodname_dotcom %}
 

content/code-security/concepts/code-scanning/ai-powered-security-detections.md

@@ -50,7 +50,7 @@ Each finding includes a description of the security issue and an explanation of
 
 AI-powered security detections are designed to cover languages and frameworks that are not currently supported by {% data variables.product.prodname_codeql %}. This includes, but is not limited to, languages such as PHP, Shell/Bash, Terraform configuration (HCL), and Dockerfiles, as well as framework coverage gaps such as JSP for Java and Blazor for C#.
 
-For a full list of languages supported by {% data variables.product.prodname_codeql %}, see [AUTOTITLE](/code-security/concepts/code-scanning/codeql/about-code-scanning-with-codeql).
+For a full list of languages supported by {% data variables.product.prodname_codeql %}, see [AUTOTITLE](/code-security/concepts/code-scanning/codeql/codeql-code-scanning).
 
 ## Detection categories
 
@@ -73,5 +73,5 @@ AI-powered security detections are not allowed at the enterprise level by defaul
 You do not need to select a model to enable AI-powered security detections.
 
 * **Enterprise**: The **AI Findings** policy under "Code Security" controls whether organizations can enable the feature. See [AUTOTITLE](/admin/enforcing-policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-code-security-and-analysis-for-your-enterprise#enforcing-a-policy-to-manage-the-use-of-ai-powered-security-detections-in-your-enterprises-repositories).
-* **Organization**: The **AI findings** setting under "Code scanning" enables AI-powered detections for repositories in the organization. See [AUTOTITLE](/code-security/how-tos/secure-at-scale/configure-organization-security/establish-complete-coverage/configuring-global-security-settings-for-your-organization#enabling-ai-powered-security-detections).
+* **Organization**: The **AI findings** setting under "Code scanning" enables AI-powered detections for repositories in the organization. See [AUTOTITLE](/code-security/how-tos/secure-at-scale/configure-organization-security/establish-complete-coverage/configure-global-settings#enabling-ai-powered-security-detections).
 * **Repository**: The **AI findings** toggle under "Code scanning" enables or disables AI-powered detections for the individual repository. Repositories inherit the organization setting but can opt out individually.