[Improvement]: Get started (phase 1): Moving some articles out of Get started -> Quickstart #12380 (#47047)

Co-authored-by: Peter Bengtsson <mail@peterbe.com>
2025-12-19 18:10:59 -05:00 · 2024-01-18 16:43:57 +01:00
parent 3a034e6401
commit 48e7c72a49
29 changed files with 48 additions and 42 deletions
--- a/.github/CONTRIBUTING.md
+++ b/.github/CONTRIBUTING.md
@@ -13,8 +13,8 @@ Use the table of contents icon <img src="/contributing/images/table-of-contents.
 To get an overview of the project, read the [README](README.md) file. Here are some resources to help you get started with open source contributions:

 - [Finding ways to contribute to open source on GitHub](https://docs.github.com/en/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github)
- [Set up Git](https://docs.github.com/en/get-started/quickstart/set-up-git)
- [GitHub flow](https://docs.github.com/en/get-started/quickstart/github-flow)
+- [Set up Git](https://docs.github.com/en/get-started/getting-started-with-git/set-up-git)
+- [GitHub flow](https://docs.github.com/en/get-started/using-github/github-flow)
 - [Collaborating with pull requests](https://docs.github.com/en/github/collaborating-with-pull-requests)


--- a/.github/workflows/sync-search-pr.yml
+++ b/.github/workflows/sync-search-pr.yml
@@ -6,6 +6,7 @@ name: Sync search - PR
 # **Who does it impact**: Docs engineering

 on:
+  workflow_dispatch:
  pull_request:
    paths:
      - 'src/search/**'
--- a/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md
+++ b/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md
@@ -68,7 +68,7 @@ Date: Sun, 27 Apr 2014 15:36:39 +0530
 Subject: [PATCH] updated index for better welcome message
 ```

-The email address in the `From:` field is the address that was set in the [local git config settings](/get-started/quickstart/set-up-git). In this example, the email address used for the commit is `octocat@nowhere.com`.
+The email address in the `From:` field is the address that was set in the [local git config settings](/get-started/getting-started-with-git/set-up-git). In this example, the email address used for the commit is `octocat@nowhere.com`.

 If the email address used for the commit is not connected to your account on {% data variables.location.product_location %}, {% ifversion ghae %}change the email address used to author commits in Git. For more information, see "[AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address#setting-your-commit-email-address-in-git)."{% else %}you must [add the email address](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account) to your account on {% data variables.location.product_location %}. Your contributions graph will be rebuilt automatically when you add the new address.{% endif %}

--- a/content/actions/creating-actions/releasing-and-maintaining-actions.md
+++ b/content/actions/creating-actions/releasing-and-maintaining-actions.md
@@ -56,7 +56,7 @@ To support the developer process in the next section, add two {% data variables.

 Here is an example process that you can follow to automatically run tests, create a release{% ifversion fpt or ghec%} and publish to {% data variables.product.prodname_marketplace %}{% endif %}, and publish your action.

-1. Do feature work in branches per GitHub flow. For more information, see "[AUTOTITLE](/get-started/quickstart/github-flow)."
+1. Do feature work in branches per GitHub flow. For more information, see "[AUTOTITLE](/get-started/using-github/github-flow)."
   - Whenever a commit is pushed to the feature branch, your testing workflow will automatically run the tests.

 1. Create pull requests to the `main` branch to initiate discussion and review, merging when ready.
--- a/content/contributing/writing-for-github-docs/using-markdown-and-liquid-in-github-docs.md
+++ b/content/contributing/writing-for-github-docs/using-markdown-and-liquid-in-github-docs.md
@@ -399,17 +399,17 @@ Because the site is dynamic, it does not build HTML files for each different ver

 For example, an article that is available in currently supported versions will have permalink URLs like the following:

- `/en/get-started/quickstart/set-up-git`
- `/en/enterprise-cloud@latest/get-started/quickstart/set-up-git`
- `/en/enterprise-server@3.10/get-started/quickstart/set-up-git`
- `/en/enterprise-server@3.9/get-started/quickstart/set-up-git`
- `/en/enterprise-server@3.8/get-started/quickstart/set-up-git`
- `/en/enterprise-server@3.7/get-started/quickstart/set-up-git`
- `/en/enterprise-server@3.6/get-started/quickstart/set-up-git`
+- `/en/get-started/getting-started-with-git/set-up-git`
+- `/en/enterprise-cloud@latest/get-started/getting-started-with-git/set-up-git`
+- `/en/enterprise-server@3.10/get-started/getting-started-with-git/set-up-git`
+- `/en/enterprise-server@3.9/get-started/getting-started-with-git/set-up-git`
+- `/en/enterprise-server@3.8/get-started/getting-started-with-git/set-up-git`
+- `/en/enterprise-server@3.7/get-started/getting-started-with-git/set-up-git`
+- `/en/enterprise-server@3.6/get-started/getting-started-with-git/set-up-git`

 An article that is not available in {% data variables.product.prodname_ghe_server %} will have just one permalink:

- `/en/get-started/quickstart/set-up-git`
+- `/en/get-started/getting-started-with-git/set-up-git`

 {% note %}

--- a/content/get-started/exploring-projects-on-github/contributing-to-a-project.md
+++ b/content/get-started/exploring-projects-on-github/contributing-to-a-project.md
@@ -104,7 +104,7 @@ gh repo fork REPOSITORY --clone=true

 ## Creating a branch to work on

-Before making changes to the project, you should create a new branch and check it out. By keeping changes in their own branch, you follow GitHub Flow and ensure that it will be easier to contribute to the same project again in the future. For more information, see "[AUTOTITLE](/get-started/quickstart/github-flow#following-github-flow)."
+Before making changes to the project, you should create a new branch and check it out. By keeping changes in their own branch, you follow GitHub Flow and ensure that it will be easier to contribute to the same project again in the future. For more information, see "[AUTOTITLE](/get-started/using-github/github-flow#following-github-flow)."

 {% webui %}

--- a/content/get-started/getting-started-with-git/git-cheatsheet.md
+++ b/content/get-started/getting-started-with-git/git-cheatsheet.md
@@ -4,6 +4,7 @@ redirect_from:
  - /articles/git-cheatsheet
  - /github/getting-started-with-github/git-cheatsheet
  - /github/getting-started-with-github/quickstart/git-cheatsheet
+  - /get-started/quickstart/git-cheatsheet
 versions:
  fpt: '*'
  ghes: '*'
--- a/content/get-started/getting-started-with-git/git-workflows.md
+++ b/content/get-started/getting-started-with-git/git-workflows.md
@@ -13,4 +13,4 @@ versions:
  ghae: '*'
  ghec: '*'
 ---
-You can adopt the {% data variables.product.prodname_dotcom %} flow method to standardize how your team functions and collaborates on {% data variables.product.prodname_dotcom %}. For more information, see "[AUTOTITLE](/get-started/quickstart/github-flow)."
+You can adopt the {% data variables.product.prodname_dotcom %} flow method to standardize how your team functions and collaborates on {% data variables.product.prodname_dotcom %}. For more information, see "[AUTOTITLE](/get-started/using-github/github-flow)."
--- a/content/get-started/getting-started-with-git/index.md
+++ b/content/get-started/getting-started-with-git/index.md
@@ -13,6 +13,7 @@ versions:
  ghae: '*'
  ghec: '*'
 children:
+  - /set-up-git
  - /setting-your-username-in-git
  - /caching-your-github-credentials-in-git
  - /why-is-git-always-asking-for-my-password
@@ -23,5 +24,5 @@ children:
  - /associating-text-editors-with-git
  - /configuring-git-to-handle-line-endings
  - /ignoring-files
+  - /git-cheatsheet
 ---
-
--- a/content/get-started/getting-started-with-git/set-up-git.md
+++ b/content/get-started/getting-started-with-git/set-up-git.md
@@ -12,6 +12,7 @@ redirect_from:
  - /articles/set-up-git
  - /github/getting-started-with-github/set-up-git
  - /github/getting-started-with-github/quickstart/set-up-git
+  - /get-started/quickstart/set-up-git
 intro: 'At the heart of {% data variables.product.prodname_dotcom %} is an open-source version control system (VCS) called Git. Git is responsible for everything {% data variables.product.prodname_dotcom %}-related that happens locally on your computer.'
 versions:
  fpt: '*'
--- a/content/get-started/index.md
+++ b/content/get-started/index.md
@@ -35,7 +35,7 @@ featuredLinks:
  popular:
    - /get-started/quickstart/creating-an-account-on-github
    - /get-started/quickstart/hello-world
-    - /get-started/quickstart/set-up-git
+    - /get-started/getting-started-with-git/set-up-git
    - /get-started/using-github-docs/about-versions-of-github-docs
    - /get-started/quickstart/github-glossary
    - /get-started/accessibility/keyboard-shortcuts
--- a/content/get-started/onboarding/getting-started-with-your-github-account.md
+++ b/content/get-started/onboarding/getting-started-with-your-github-account.md
@@ -72,11 +72,11 @@ To best use {% data variables.product.product_name %}, you'll need to set up Git

 ### 1. Learning Git

-{% data variables.product.prodname_dotcom %}'s collaborative approach to development depends on publishing commits from your local repository to {% data variables.product.product_name %} for other people to view, fetch, and update using Git. For more information about Git, see the "[Git Handbook](https://guides.github.com/introduction/git-handbook/)" guide. For more information about how Git is used on {% data variables.product.product_name %}, see "[AUTOTITLE](/get-started/quickstart/github-flow)."
+{% data variables.product.prodname_dotcom %}'s collaborative approach to development depends on publishing commits from your local repository to {% data variables.product.product_name %} for other people to view, fetch, and update using Git. For more information about Git, see the "[Git Handbook](https://guides.github.com/introduction/git-handbook/)" guide. For more information about how Git is used on {% data variables.product.product_name %}, see "[AUTOTITLE](/get-started/using-github/github-flow)."

 ### 2. Setting up Git

-If you plan to use Git locally on your computer, whether through the command line, an IDE or text editor, you will need to install and set up Git. For more information, see "[AUTOTITLE](/get-started/quickstart/set-up-git)."
+If you plan to use Git locally on your computer, whether through the command line, an IDE or text editor, you will need to install and set up Git. For more information, see "[AUTOTITLE](/get-started/getting-started-with-git/set-up-git)."

 If you prefer to use a visual interface, you can download and use {% data variables.product.prodname_desktop %}. {% data variables.product.prodname_desktop %} comes packaged with Git, so there is no need to install Git separately. For more information, see "[AUTOTITLE](/desktop/overview/getting-started-with-github-desktop)."

--- a/content/get-started/quickstart/hello-world.md
+++ b/content/get-started/quickstart/hello-world.md
@@ -153,4 +153,4 @@ Here's what you accomplished in this tutorial:

 Take a look at your {% data variables.product.product_name %} profile and you'll see your work reflected on your contribution graph.

-For more information about the power of branches and pull requests, see "[AUTOTITLE](/get-started/quickstart/github-flow)." For more information about getting started with {% data variables.product.product_name %}, see the other guides in the [getting started quickstart](/get-started/quickstart).
+For more information about the power of branches and pull requests, see "[AUTOTITLE](/get-started/using-github/github-flow)." For more information about getting started with {% data variables.product.product_name %}, see the other guides in the [getting started quickstart](/get-started/quickstart).
--- a/content/get-started/quickstart/index.md
+++ b/content/get-started/quickstart/index.md
@@ -17,13 +17,8 @@ children:
  - /hello-world
  - /finding-inspiration-on-github
  - /downloading-files-from-github
-  - /set-up-git
-  - /github-flow
-  - /communicating-on-github
-  - /github-glossary
-  - /git-cheatsheet
  - /git-and-github-learning-resources
+  - /github-glossary
 redirect_from:
  - /github/getting-started-with-github/quickstart
 ---
-
--- a/content/get-started/using-git/about-git.md
+++ b/content/get-started/using-git/about-git.md
@@ -43,7 +43,7 @@ Through platforms like {% data variables.product.product_name %}, Git also provi

 {% data variables.product.product_name %} hosts Git repositories and provides developers with tools to ship better code through command line features, issues (threaded discussions), pull requests, code review, or the use of a collection of free and for-purchase apps in the {% data variables.product.prodname_marketplace %}. With collaboration layers like the {% data variables.product.product_name %} flow, a community of 100 million developers, and an ecosystem with hundreds of integrations, {% data variables.product.product_name %} changes the way software is built.

-{% data variables.product.product_name %} builds collaboration directly into the development process. Work is organized into repositories where developers can outline requirements or direction and set expectations for team members. Then, using the {% data variables.product.product_name %} flow, developers simply create a branch to work on updates, commit changes to save them, open a pull request to propose and discuss changes, and merge pull requests once everyone is on the same page. For more information, see "[AUTOTITLE](/get-started/quickstart/github-flow)."
+{% data variables.product.product_name %} builds collaboration directly into the development process. Work is organized into repositories where developers can outline requirements or direction and set expectations for team members. Then, using the {% data variables.product.product_name %} flow, developers simply create a branch to work on updates, commit changes to save them, open a pull request to propose and discuss changes, and merge pull requests once everyone is on the same page. For more information, see "[AUTOTITLE](/get-started/using-github/github-flow)."

 For {% data variables.product.prodname_dotcom %} plans and costs, see {% data variables.product.pricing_link %}. For information on how {% data variables.product.prodname_enterprise %} compares to other options, see [Comparing GitHub to other DevOps solutions](https://resources.github.com/devops/tools/compare/).

--- a/content/get-started/using-git/pushing-commits-to-a-remote-repository.md
+++ b/content/get-started/using-git/pushing-commits-to-a-remote-repository.md
@@ -115,7 +115,7 @@ For more information on working with forks, see "[AUTOTITLE](/pull-requests/coll

 - [The "Remotes" chapter from the "Pro Git" book](https://git-scm.com/book/ch5-2.html)
 - [`git remote` main page](https://git-scm.com/docs/git-remote.html)
- "[AUTOTITLE](/get-started/quickstart/git-cheatsheet)"
+- "[AUTOTITLE](/get-started/getting-started-with-git/git-cheatsheet)"
 - "[AUTOTITLE](/get-started/getting-started-with-git/git-workflows)"
 - "[Git Handbook](https://guides.github.com/introduction/git-handbook/)"{% ifversion fpt or ghec %}
 - "[AUTOTITLE](/get-started/using-git/troubleshooting-the-2-gb-push-limit)"{% endif %}
--- a/content/get-started/using-github/communicating-on-github.md
+++ b/content/get-started/using-github/communicating-on-github.md
@@ -7,6 +7,7 @@ redirect_from:
  - /github/collaborating-with-issues-and-pull-requests/about-conversations-on-github
  - /github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github
  - /github/getting-started-with-github/quickstart/communicating-on-github
+  - /get-started/quickstart/communicating-on-github
 versions:
  fpt: '*'
  ghes: '*'
--- a/content/get-started/using-github/connecting-to-github.md
+++ b/content/get-started/using-github/connecting-to-github.md
@@ -24,7 +24,7 @@ If you're new to {% data variables.product.prodname_dotcom %}, a good way to sta

 ## Getting started

-In the user interface on {% data variables.location.product_location %}, you can perform the whole "{% data variables.product.prodname_dotcom %} flow" for contributing to a repository, including creating a branch or fork, editing and previewing files, committing your changes, and creating a pull request. You can also upload files from your computer or download them from the repository. For more information, see "[AUTOTITLE](/get-started/quickstart/github-flow)."
+In the user interface on {% data variables.location.product_location %}, you can perform the whole "{% data variables.product.prodname_dotcom %} flow" for contributing to a repository, including creating a branch or fork, editing and previewing files, committing your changes, and creating a pull request. You can also upload files from your computer or download them from the repository. For more information, see "[AUTOTITLE](/get-started/using-github/github-flow)."

 Working directly on {% data variables.location.product_location %} is often the quickest way to contribute to a repository, for the following reasons.

@@ -57,7 +57,7 @@ If you haven't worked with a {% data variables.product.prodname_dotcom %} reposi

 There are several tools you can use to connect to {% data variables.product.prodname_dotcom %} from your desktop. These tools allow you to authenticate to {% data variables.product.prodname_dotcom %}, clone a repository, track your changes, and push the changes to {% data variables.product.prodname_dotcom %}.

- If you want a lot of control and flexibility, you can use the command line. You'll need to install Git and be familiar with some basic Git commands. You can also install {% data variables.product.prodname_cli %}, a command-line interface that lets you perform many actions on {% data variables.product.prodname_dotcom %}, such as creating a pull request or forking a repository. For more information, see "[AUTOTITLE](/get-started/quickstart/set-up-git)" and "[AUTOTITLE](/github-cli/github-cli/about-github-cli)."
+- If you want a lot of control and flexibility, you can use the command line. You'll need to install Git and be familiar with some basic Git commands. You can also install {% data variables.product.prodname_cli %}, a command-line interface that lets you perform many actions on {% data variables.product.prodname_dotcom %}, such as creating a pull request or forking a repository. For more information, see "[AUTOTITLE](/get-started/getting-started-with-git/set-up-git)" and "[AUTOTITLE](/github-cli/github-cli/about-github-cli)."
 - If you'd prefer to use a visual interface, you can use a visual Git client such as {% data variables.product.prodname_desktop %}. With {% data variables.product.prodname_desktop %}, you can visualize the changes you're making and access most Git commands through a visual interface, so you don't need to memorize any commands. For more information, see "[AUTOTITLE](/desktop/overview/about-github-desktop)."
 - If you want to work in one place, you can often do most things from your editor. An editor such as {% data variables.product.prodname_vscode_shortname %} includes an integrated terminal and buttons for common Git commands, so you can edit files and push your changes to {% data variables.product.prodname_dotcom %} all from one place. You can also install an extension to work directly with pull requests and issues on {% data variables.product.prodname_dotcom %}. To get started, see [Download {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/download).

@@ -78,7 +78,7 @@ For more information about how to authenticate to {% data variables.product.prod
 {%- endif %}
 | **{% data variables.product.prodname_desktop %}** | You want to work with files locally, and would prefer a visual interface to use Git, visualize changes, and interact with {% data variables.product.product_name %}. For more information, see "[AUTOTITLE](/desktop/overview/about-github-desktop)." | Desktop |
 | **IDE or text editor**  | You're working with more complex files and projects and want everything in one place. | Desktop |
-| **Command-line Git and {% data variables.product.prodname_cli %}** | You're used to working from the command line and want to avoid switching context, or you need to access a complex Git command that isn't integrated into visual interfaces. For more information, see "[AUTOTITLE](/get-started/quickstart/set-up-git)" and "[AUTOTITLE](/github-cli/github-cli/about-github-cli)." | Desktop |
+| **Command-line Git and {% data variables.product.prodname_cli %}** | You're used to working from the command line and want to avoid switching context, or you need to access a complex Git command that isn't integrated into visual interfaces. For more information, see "[AUTOTITLE](/get-started/getting-started-with-git/set-up-git)" and "[AUTOTITLE](/github-cli/github-cli/about-github-cli)." | Desktop |
 | **{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API** | You want to automate common tasks such as backing up your data, or create integrations that extend {% data variables.product.prodname_dotcom %}. For more information, see "[AUTOTITLE](/rest/overview/about-githubs-apis)." | Browser or desktop |

 ## Further reading
--- a/content/get-started/using-github/github-flow.md
+++ b/content/get-started/using-github/github-flow.md
@@ -8,6 +8,7 @@ redirect_from:
  - /github/collaborating-with-issues-and-pull-requests/github-flow
  - /github/getting-started-with-github/github-flow
  - /github/getting-started-with-github/quickstart/github-flow
+  - /get-started/quickstart/github-flow
 versions:
  fpt: '*'
  ghes: '*'
--- a/content/get-started/using-github/index.md
+++ b/content/get-started/using-github/index.md
@@ -10,11 +10,12 @@ versions:
  ghae: '*'
  ghec: '*'
 children:
+  - /github-flow
  - /connecting-to-github
+  - /communicating-on-github
  - /exploring-early-access-releases-with-feature-preview
  - /supported-browsers
  - /github-mobile
  - /allowing-access-to-githubs-services-from-a-restricted-network
  - /troubleshooting-connectivity-problems
 ---
-
--- a/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/quickstart-for-writing-on-github.md
+++ b/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/quickstart-for-writing-on-github.md
@@ -245,4 +245,4 @@ Committing directly to the `main` branch will make your changes visible to any v
 ## Next steps

 - Continue to learn about advanced formatting features. For example, see {% ifversion fpt or ghec %}"[AUTOTITLE](/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams)" and {% endif %}"[AUTOTITLE](/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks)."
- Use your new skills as you communicate across GitHub, in issues, pull requests, and discussions. For more information, see "[AUTOTITLE](/get-started/quickstart/communicating-on-github)."
+- Use your new skills as you communicate across GitHub, in issues, pull requests, and discussions. For more information, see "[AUTOTITLE](/get-started/using-github/communicating-on-github)."
--- a/content/index.md
+++ b/content/index.md
@@ -2,7 +2,7 @@
 title: '{% data variables.product.product_name %}{% ifversion fpt or ghec%}.com{% endif %} Help Documentation'
 featuredLinks:
  gettingStarted:
-    - /get-started/quickstart/set-up-git
+    - /get-started/getting-started-with-git/set-up-git
    - /authentication/connecting-to-github-with-ssh
    - /repositories/creating-and-managing-repositories
    - /get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax
@@ -169,4 +169,3 @@ externalProducts:
    href: 'https://docs.npmjs.com/'
    external: true
 ---
-
--- a/content/issues/tracking-your-work-with-issues/about-issues.md
+++ b/content/issues/tracking-your-work-with-issues/about-issues.md
@@ -58,7 +58,7 @@ You can @mention collaborators who have access to your repository in an issue to

 ### Comparing issues and discussions

-Some conversations are more suitable for {% data variables.product.prodname_discussions %}. {% data reusables.discussions.you-can-use-discussions %} For guidance on when to use an issue or a discussion, see "[AUTOTITLE](/get-started/quickstart/communicating-on-github)."
+Some conversations are more suitable for {% data variables.product.prodname_discussions %}. {% data reusables.discussions.you-can-use-discussions %} For guidance on when to use an issue or a discussion, see "[AUTOTITLE](/get-started/using-github/communicating-on-github)."

 {% ifversion converting-issues-to-discussions %}When a conversation in an issue is better suited for a discussion, you can convert the issue to a discussion.{% endif %}
 {% endif %}
--- a/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md
+++ b/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md
@@ -88,7 +88,7 @@ Below we have added a task list to our Project Octocat issue, breaking it down i

 ## Making decisions as a team

-You can use issues and discussions to communicate and make decisions as a team on planned improvements or priorities for your project. Issues are useful when you create them for discussion of specific details, such as bug or performance reports, planning for the next quarter, or design for a new initiative. Discussions are useful for open-ended brainstorming or feedback, outside the codebase and across repositories. For more information, see "[AUTOTITLE](/get-started/quickstart/communicating-on-github#which-discussion-tool-should-i-use)."
+You can use issues and discussions to communicate and make decisions as a team on planned improvements or priorities for your project. Issues are useful when you create them for discussion of specific details, such as bug or performance reports, planning for the next quarter, or design for a new initiative. Discussions are useful for open-ended brainstorming or feedback, outside the codebase and across repositories. For more information, see "[AUTOTITLE](/get-started/using-github/communicating-on-github#which-discussion-tool-should-i-use)."

 As a team, you can also communicate updates on day-to-day tasks within issues so that everyone knows the status of work. For example, you can create an issue for a large feature that multiple people are working on, and each team member can add updates with their status or open questions in that issue.

--- a/content/organizations/collaborating-with-your-team/about-team-discussions.md
+++ b/content/organizations/collaborating-with-your-team/about-team-discussions.md
@@ -48,7 +48,7 @@ You can also use organization discussions to facilitate conversations across you

 ## Further reading

- "[AUTOTITLE](/get-started/quickstart/communicating-on-github)"
+- "[AUTOTITLE](/get-started/using-github/communicating-on-github)"
 - "[AUTOTITLE](/organizations/organizing-members-into-teams/about-teams)"
 - "[AUTOTITLE](/organizations/collaborating-with-your-team/creating-a-team-discussion)"
 - "[AUTOTITLE](/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion)"
--- a/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md
+++ b/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md
@@ -20,7 +20,7 @@ shortTitle: Create site with Jekyll

 ## Prerequisites

-Before you can use Jekyll to create a {% data variables.product.prodname_pages %} site, you must install Jekyll and Git. For more information, see [Installation](https://jekyllrb.com/docs/installation/) in the Jekyll documentation and "[AUTOTITLE](/get-started/quickstart/set-up-git)."
+Before you can use Jekyll to create a {% data variables.product.prodname_pages %} site, you must install Jekyll and Git. For more information, see [Installation](https://jekyllrb.com/docs/installation/) in the Jekyll documentation and "[AUTOTITLE](/get-started/getting-started-with-git/set-up-git)."

 {% data reusables.pages.recommend-bundler %}

--- a/content/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo.md
+++ b/content/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo.md
@@ -49,7 +49,7 @@ When creating your public repository from a fork of someone's project, make sure

 ## Prerequisites

-If you haven't yet, first set up Git and authentication with {% data variables.location.product_location %} from Git. For more information, see "[AUTOTITLE](/get-started/quickstart/set-up-git)."
+If you haven't yet, first set up Git and authentication with {% data variables.location.product_location %} from Git. For more information, see "[AUTOTITLE](/get-started/getting-started-with-git/set-up-git)."

 ## Forking a repository

@@ -234,6 +234,11 @@ Fork a repository to start contributing to a project. {% data reusables.reposito

 You have now forked a repository, practiced cloning your fork, and configured an upstream repository.

+<<<<<<< HEAD:content/get-started/quickstart/fork-a-repo.md
+- For more information about cloning the fork and syncing the changes in a forked repository from your computer, see "[AUTOTITLE](/get-started/getting-started-with-git/set-up-git)."
+
+=======
+>>>>>>> main:content/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo.md
 - You can also create a new repository where you can put all your projects and share the code on {% data variables.product.prodname_dotcom %}. {% data reusables.getting-started.create-a-repository %}"

 - {% data reusables.getting-started.being-social %}
--- a/content/repositories/creating-and-managing-repositories/quickstart-for-repositories.md
+++ b/content/repositories/creating-and-managing-repositories/quickstart-for-repositories.md
@@ -119,7 +119,7 @@ You have now created a repository, including a _README_ file, and created your f

 {% webui %}

- You can now clone a {% data variables.product.prodname_dotcom %} repository to create a local copy on your computer. From your local repository you can commit, and create a pull request to update the changes in the upstream repository. For more information, see "[AUTOTITLE](/repositories/creating-and-managing-repositories/cloning-a-repository)" and "[AUTOTITLE](/get-started/quickstart/set-up-git)."
+- You can now clone a {% data variables.product.prodname_dotcom %} repository to create a local copy on your computer. From your local repository you can commit, and create a pull request to update the changes in the upstream repository. For more information, see "[AUTOTITLE](/repositories/creating-and-managing-repositories/cloning-a-repository)" and "[AUTOTITLE](/get-started/getting-started-with-git/set-up-git)."

 {% endwebui %}

--- a/data/reusables/getting-started/set-up-git.md
+++ b/data/reusables/getting-started/set-up-git.md
@@ -1 +1 @@
-Synchronizing {% data variables.product.prodname_dotcom %} repositories with your computer allows you to work locally and push your changes to {% data variables.product.prodname_dotcom %}. For more information, see “[Set up Git](/get-started/quickstart/set-up-git).”
+Synchronizing {% data variables.product.prodname_dotcom %} repositories with your computer allows you to work locally and push your changes to {% data variables.product.prodname_dotcom %}. For more information, see “[Set up Git](/get-started/getting-started-with-git/set-up-git).”