Branch was updated using the 'autoupdate branch' Actions workflow.

Author: Octomerger

.github/workflows/first-responder-docs-content.yml

@@ -36,7 +36,7 @@ jobs:
               issue_number: issueNumber
             })
             const teamMembers = await github.request(
-              `/orgs/github/teams/docs/members`
+              `/orgs/github/teams/docs/members?per_page=100`
             )
             const logins = teamMembers.data.map(member => member.login)
             // ignore PRs opened by docs bot accounts

.github/workflows/move-ready-to-merge-issues.yaml

@@ -5,7 +5,7 @@ name: Move and unlabel ready to merge issues
 # **Who does it impact**: Open source contributors, open-source maintainers.
 
 on:
-  pull_request:
+  pull_request_target:
     types:
       - labeled
 

.github/workflows/triage-pull-requests.yml

@@ -5,7 +5,7 @@ name: Triage new pull requests
 # **Who does it impact**:
 
 on:
-  pull_request:
+  pull_request_target:
     types:
       - reopened
       - opened

.pa11yci

@@ -13,17 +13,16 @@
     "http://localhost:4001/en/actions",
     "http://localhost:4001/en/github/authenticating-to-github/creating-a-personal-access-token",
     "http://localhost:4001/en/github/authenticating-to-github/checking-for-existing-ssh-keys",
-    "http://localhost:4001/en/github/using-git/changing-a-remotes-url",
+    "http://localhost:4001/en/github/getting-started-with-github/managing-remote-repositories",
     "http://localhost:4001/en/github/getting-started-with-github/set-up-git",
     "http://localhost:4001/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository",
     "http://localhost:4001/en/github/writing-on-github/basic-writing-and-formatting-syntax",
     "http://localhost:4001/en/actions/reference/workflow-syntax-for-github-actions",
-    "http://localhost:4001/en/github/using-git/which-remote-url-should-i-use",
+    "http://localhost:4001/en/github/getting-started-with-github/about-remote-repositories",
     "http://localhost:4001/en/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line",
-    "http://localhost:4001/en/github/using-git/setting-your-username-in-git",
+    "http://localhost:4001/en/github/getting-started-with-github/setting-your-username-in-git",
     "http://localhost:4001/en/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address",
     "http://localhost:4001/en/github/authenticating-to-github/configuring-two-factor-authentication",
-    "http://localhost:4001/en/github/using-git/adding-a-remote",
     "http://localhost:4001/en/rest",
     "http://localhost:4001/en/github/working-with-github-pages/configuring-a-custom-domain-for-your-github-pages-site",
     "http://localhost:4001/en/github/collaborating-with-issues-and-pull-requests/about-pull-requests",
@@ -55,7 +54,7 @@
     "http://localhost:4001/en/actions/getting-started-with-github-actions",
     "http://localhost:4001/en/actions/reference/events-that-trigger-workflows",
     "http://localhost:4001/en/desktop/getting-started-with-github-desktop/installing-github-desktop",
-    "http://localhost:4001/en/github/using-git/ignoring-files",
+    "http://localhost:4001/en/github/getting-started-with-github/ignoring-files",
     "http://localhost:4001/en/desktop",
     "http://localhost:4001/en/packages",
     "http://localhost:4001/en/actions/configuring-and-managing-workflows/configuring-a-workflow",
@@ -71,7 +70,7 @@
     "http://localhost:4001/en/actions/reference/context-and-expression-syntax-for-github-actions",
     "http://localhost:4001/en/github/managing-files-in-a-repository/navigating-code-on-github",
     "http://localhost:4001/en/github/teaching-and-learning-with-github-education/applying-for-a-student-developer-pack",
-    "http://localhost:4001/en/github/using-git/caching-your-github-credentials-in-git",
+    "http://localhost:4001/en/github/getting-started-with-github/caching-your-github-credentials-in-git",
     "http://localhost:4001/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request",
     "http://localhost:4001/en/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository",
     "http://localhost:4001/en/github/setting-up-and-managing-your-github-user-account/changing-your-github-username",
@@ -81,7 +80,6 @@
     "http://localhost:4001/en/actions/configuring-and-managing-workflows/using-environment-variables",
     "http://localhost:4001/en/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets",
     "http://localhost:4001/en/github/authenticating-to-github/removing-sensitive-data-from-a-repository",
-    "http://localhost:4001/en/github/using-git/removing-a-remote",
     "http://localhost:4001/en/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line",
     "http://localhost:4001/en/github/setting-up-and-managing-billing-and-payments-on-github/setting-your-billing-email",
     "http://localhost:4001/en/github/setting-up-and-managing-your-github-user-account",
@@ -90,8 +88,8 @@
     "http://localhost:4001/en/github/authenticating-to-github/about-two-factor-authentication",
     "http://localhost:4001/en/github/working-with-github-pages/about-custom-domains-and-github-pages",
     "http://localhost:4001/en/github/searching-for-information-on-github/searching-code",
-    "http://localhost:4001/en/github/using-git/configuring-git-to-handle-line-endings",
-    "http://localhost:4001/en/github/using-git/getting-changes-from-a-remote-repository",
+    "http://localhost:4001/en/github/getting-started-with-github/configuring-git-to-handle-line-endings",
+    "http://localhost:4001/en/github/getting-started-with-github/getting-changes-from-a-remote-repository",
     "http://localhost:4001/en/github/authenticating-to-github/generating-a-new-gpg-key",
     "http://localhost:4001/en/github/authenticating-to-github/accessing-github-using-two-factor-authentication",
     "http://localhost:4001/en/github/creating-cloning-and-archiving-repositories/licensing-a-repository",

content/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop.md

@@ -44,4 +44,4 @@ You can change how a fork behaves with the upstream repository in {% data variab
 {% data reusables.desktop.select-fork-behavior %}
 
 ### Further reading
-- [About remote repositories](/github/using-git/about-remote-repositories)
+- [About remote repositories](/github/getting-started-with-github/about-remote-repositories)

content/desktop/contributing-and-collaborating-using-github-desktop/syncing-your-branch.md

@@ -15,7 +15,7 @@ When you pull to your local branch, you only update your local copy of the repos
 
 To add changes from one branch to another branch, you can merge the branches. To apply changes to your branch from another branch in the same repository, you can merge the other branch into your branch on {% data variables.product.prodname_desktop %}. To request that changes from your branch are merged into another branch, in the same repository or in another repository in the network, you can create a pull request on {% data variables.product.prodname_desktop %}. For more information, see "[Merging another branch into your project branch](#merging-another-branch-into-your-project-branch)" and "[About pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)."
 
-Some workflows require or benefit from rebasing instead of merging. By rebasing you can reorder, edit, or squash commits together. For more information, see "[About Git rebase](/articles/about-git-rebase)" and "[Rebasing your project branch onto another branch](#rebasing-your-project-branch-onto-another-branch)."
+Some workflows require or benefit from rebasing instead of merging. By rebasing you can reorder, edit, or squash commits together. For more information, see "[About Git rebase](/github/getting-started-with-github/about-git-rebase)" and "[Rebasing your project branch onto another branch](#rebasing-your-project-branch-onto-another-branch)."
 
 ### Pulling to your local branch from the remote
 

content/desktop/installing-and-configuring-github-desktop/about-connections-to-github.md

@@ -11,7 +11,7 @@ versions:
 
 After you authenticate to {% data variables.product.prodname_dotcom %}, you can connect to remote repositories with {% data variables.product.prodname_desktop %}. {% data variables.product.prodname_desktop %} caches your credentials (username and password or personal access token) and uses the credentials to authenticate for each connection to the remote repository.
 
-{% data variables.product.prodname_desktop %} connects to {% data variables.product.prodname_dotcom %} using HTTPS. If you use {% data variables.product.prodname_desktop %} to access repositories that were cloned using SSH, you may encounter errors. To connect to a repository that was cloned using SSH, change the remote's URLs. For more information, see "[Changing a remote's URL](/github/using-git/changing-a-remotes-url)."
+{% data variables.product.prodname_desktop %} connects to {% data variables.product.prodname_dotcom %} using HTTPS. If you use {% data variables.product.prodname_desktop %} to access repositories that were cloned using SSH, you may encounter errors. To connect to a repository that was cloned using SSH, change the remote's URLs. For more information, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)."
 
 ### Further reading
 - "[Cloning and forking repositories from GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop)"

content/desktop/installing-and-configuring-github-desktop/creating-your-first-repository-using-github-desktop.md

@@ -42,7 +42,7 @@ If you do not wish to create and clone a tutorial repository, you can create a n
    - "Description" is an optional field that you can use to provide more information about the purpose of your repository.
    - "Local path" sets the location of your repository on your computer. By default, {% data variables.product.prodname_desktop %} creates a _GitHub_ folder inside your _Documents_ folder to store your repositories, but you can choose any location on your computer. Your new repository will be a folder inside the chosen location. For example, if you name your repository `Tutorial`, a folder named _Tutorial_ is created inside the folder you selected for your local path. {% data variables.product.prodname_desktop %} remembers your chosen location the next time you create or clone a new repository.
    - **Initialize this repository with a README** creates an initial commit with a _README.md_ file. READMEs helps people understand the purpose of your project, so we recommend selecting this and filling it out with helpful information. When someone visits your repository on {% data variables.product.product_name %}, the README is the first thing they'll see as they learn about your project. For more information, see "[About READMEs](/articles/about-readmes)."
-   - The **Git ignore** drop-down menu lets you add a custom file to ignore specific files in your local repository that you don't want to store in version control. If there's a specific language or framework that you'll be using, you can select an option from the available list. If you're just getting started, feel free to skip this selection. For more information, see "[Ignoring files](/articles/ignoring-files)."
+   - The **Git ignore** drop-down menu lets you add a custom file to ignore specific files in your local repository that you don't want to store in version control. If there's a specific language or framework that you'll be using, you can select an option from the available list. If you're just getting started, feel free to skip this selection. For more information, see "[Ignoring files](/github/getting-started-with-github/ignoring-files)."
    - The **License** drop-down menu lets you add an open-source license to a _LICENSE_ file in your repository. You don't need to worry about adding a license right away. For more information about available open-source licenses and how to add them to your repository, see "[Licensing a repository](/articles/licensing-a-repository)."
 3. Click **Create repository**.
 
@@ -107,6 +107,6 @@ Now that you've created and published your repository, you're ready to make chan
 You've now created a repository, published the repository to {% data variables.product.product_name %}, made a commit, and pushed your changes to {% data variables.product.product_name %}. You can follow this same workflow when contributing to other projects that you create or collaborate on.
 
 ### Further reading
-- "[Learning about Git](/github/using-git/learning-about-git)"
+- "[Getting started with Git](/github/getting-started-with-github/getting-started-with-git)"
 - "[Learning about {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/learning-about-github)"
 - "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)"

content/desktop/installing-and-configuring-github-desktop/getting-started-with-github-desktop.md

@@ -13,7 +13,7 @@ This guide will help you get started with {% data variables.product.prodname_des
 
 You might find it helpful to have a basic understanding of Git and {% data variables.product.prodname_dotcom %} before getting started with {% data variables.product.prodname_desktop %}. For more information, see the following articles.
 
-- "[Learning about Git](/github/using-git/learning-about-git)"
+- "[Using Git](/github/getting-started-with-github/using-git)"
 - "[Learning about {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/learning-about-github)"
 - "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)"
 

content/developers/apps/creating-ci-tests-with-the-checks-api.md

@@ -724,7 +724,7 @@ The RuboCop tool [offers](https://docs.rubocop.org/rubocop/usage/basic_usage.htm
 
 To push to a repository, your app must have write permissions for "Repository contents." You set that permission back in [Step 2.2. Cloning the repository](#step-22-cloning-the-repository) to **Read & write**, so you're all set.
 
-In order to commit files, Git must know which [username](/articles/setting-your-username-in-git/) and [email](/articles/setting-your-commit-email-address-in-git/) to associate with the commit. Add two more environment variables in your `.env` file to store the name (`GITHUB_APP_USER_NAME`) and email (`GITHUB_APP_USER_EMAIL`) settings. Your name can be the name of your app and the email can be any email you'd like for this example. For example:
+In order to commit files, Git must know which [username](/github/getting-started-with-github/setting-your-username-in-git/) and [email](/articles/setting-your-commit-email-address-in-git/) to associate with the commit. Add two more environment variables in your `.env` file to store the name (`GITHUB_APP_USER_NAME`) and email (`GITHUB_APP_USER_EMAIL`) settings. Your name can be the name of your app and the email can be any email you'd like for this example. For example:
 
 ```ini
 GITHUB_APP_USER_NAME=Octoapp