jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-19 18:10:59 -05:00
Code Issues Projects Releases Wiki Activity

Rename "Getting started with Git" to "Git basics" (#54512)

Browse Source
This commit is contained in:
Sam Browning
2025-02-26 10:48:47 -05:00
committed by GitHub
parent acdc94df25
commit 6b37bf8c66
53 changed files with 92 additions and 79 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
.github/CONTRIBUTING.md vendored
View File

@@ -13,7 +13,7 @@ Use the table of contents icon <img alt="Table of contents icon" src="/contribut
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/getting-started-with-git/set-up-git)
- [Set up Git](https://docs.github.com/en/get-started/git-basics/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)

2
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
View File

@@ -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/getting-started-with-git/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/git-basics/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.product.prodname_dotcom %}, 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.product.prodname_dotcom %}. Your contributions graph will be rebuilt automatically when you add the new address.

2
content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md
View File

@@ -41,7 +41,7 @@ shortTitle: Find your username or email
## Finding your username in your `user.name` configuration
During set up, you may have [set your username in Git](/get-started/getting-started-with-git/setting-your-username-in-git). If so, you can review the value of this configuration setting:
During set up, you may have [set your username in Git](/get-started/git-basics/setting-your-username-in-git). If so, you can review the value of this configuration setting:
```shell
$ git config user.name

2
content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-user-account-settings/changing-your-github-username.md
View File

@@ -70,7 +70,7 @@ After you change your username, {% data variables.product.github %} will automat
* Web links to your existing repositories will continue to work. This can take a few minutes to complete after you make the change.
* Command line pushes from your local repository clones to the old remote tracking URLs will continue to work.
If the new owner of your old username creates a repository with the same name as your repository, that will override the redirect entry and your redirect will stop working. Because of this possibility, we recommend you update all existing remote repository URLs after changing your username. For more information, see [AUTOTITLE](/get-started/getting-started-with-git/managing-remote-repositories).
If the new owner of your old username creates a repository with the same name as your repository, that will override the redirect entry and your redirect will stop working. Because of this possibility, we recommend you update all existing remote repository URLs after changing your username. For more information, see [AUTOTITLE](/get-started/git-basics/managing-remote-repositories).
## Links to your previous profile page

2
content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/merging-multiple-personal-accounts.md
View File

@@ -36,7 +36,7 @@ shortTitle: Merge multiple accounts
> * Achievements are not able to be transferred between accounts.
1. [Transfer any repositories](/repositories/creating-and-managing-repositories/transferring-a-repository) from the account you want to delete to the account you want to keep. Issues, pull requests, and wikis are transferred as well. Verify the repositories exist on the account you want to keep.
1. [Update the remote URLs](/get-started/getting-started-with-git/managing-remote-repositories) in any local clones of the repositories that were moved.
1. [Update the remote URLs](/get-started/git-basics/managing-remote-repositories) in any local clones of the repositories that were moved.
1. To attribute past commits to the new account, add the email address you used to author the commits to the account you're keeping. For more information, see [AUTOTITLE](/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#your-local-git-commit-email-isnt-connected-to-your-account)
1. [Delete the account](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/deleting-your-personal-account) you no longer want to use.

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

@@ -49,7 +49,7 @@ The following sections will lead you through setting up the following components
1. Create a repository to store the code for your app. For more information, see [AUTOTITLE](/repositories/creating-and-managing-repositories/creating-a-new-repository).
1. Clone your repository from the previous step. For more information, see [AUTOTITLE](/repositories/creating-and-managing-repositories/cloning-a-repository). You may use a local clone or {% data variables.product.prodname_github_codespaces %}.
1. In a terminal, navigate to the directory where your clone is stored.
1. If the directory doesn't already include a `.gitignore` file, add a `.gitignore` file. You will add content to this file later. For more information about `.gitignore` files, see [AUTOTITLE](/get-started/getting-started-with-git/ignoring-files).
1. If the directory doesn't already include a `.gitignore` file, add a `.gitignore` file. You will add content to this file later. For more information about `.gitignore` files, see [AUTOTITLE](/get-started/git-basics/ignoring-files).
You will add more code to this repository in later steps.

2
content/apps/creating-github-apps/writing-code-for-a-github-app/building-a-login-with-github-button-with-a-github-app.md
View File

@@ -86,7 +86,7 @@ This tutorial will show you how to store the client ID and client secret in envi
1. On the app's settings page, click **Generate a new client secret**. You will add the client secret to a `.env` file in a following step.
1. Create a file called `.env` at the same level as your `Gemfile`.
1. If your project doesn't already have a `.gitignore` file, create a `.gitignore` file at the same level as your `Gemfile`.
1. Add `.env` to your `.gitignore` file. This will prevent you from accidentally committing your client secret. For more information about `.gitignore` files, see [AUTOTITLE](/get-started/getting-started-with-git/ignoring-files).
1. Add `.env` to your `.gitignore` file. This will prevent you from accidentally committing your client secret. For more information about `.gitignore` files, see [AUTOTITLE](/get-started/git-basics/ignoring-files).
1. Add the following contents to your `.env` file. Replace `YOUR_CLIENT_ID` with the client ID of your app. Replace `YOUR_CLIENT_SECRET` with the client secret for your app.
```text

2
content/apps/creating-github-apps/writing-code-for-a-github-app/building-ci-checks-with-a-github-app.md
View File

@@ -78,7 +78,7 @@ The following sections will lead you through setting up the following components
1. Clone your repository from the previous step. For more information, see [AUTOTITLE](/repositories/creating-and-managing-repositories/cloning-a-repository). You may use a local clone or {% data variables.product.prodname_github_codespaces %}.
1. In a terminal, navigate to the directory where your clone is stored.
1. Create a Ruby file named `server.rb`. This file will contain all the code for your app. You will add content to this file later.
1. If the directory doesn't already include a `.gitignore` file, add a `.gitignore` file. You will add content to this file later. For more information about `.gitignore` files, see [AUTOTITLE](/get-started/getting-started-with-git/ignoring-files).
1. If the directory doesn't already include a `.gitignore` file, add a `.gitignore` file. You will add content to this file later. For more information about `.gitignore` files, see [AUTOTITLE](/get-started/git-basics/ignoring-files).
1. Create a file named `Gemfile`. This file will describe the gem dependencies that your Ruby code needs. Add the following contents to your `Gemfile`:
```ruby copy

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

@@ -68,7 +68,7 @@ Make sure that you are on a secure machine before performing these steps since y
### Create a `.env` file
Your cloned repository includes `.env` in the `.gitignore` file. This will prevent you from accidentally committing your app's credentials. For more information about `.gitignore` files, see [AUTOTITLE](/get-started/getting-started-with-git/ignoring-files).
Your cloned repository includes `.env` in the `.gitignore` file. This will prevent you from accidentally committing your app's credentials. For more information about `.gitignore` files, see [AUTOTITLE](/get-started/git-basics/ignoring-files).
1. Navigate to the directory where your clone of [github/github-app-js-sample](https://github.com/github/github-app-js-sample) is stored.
1. Create a file called `.env` at the top level of this directory.

2
content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md
View File

@@ -33,7 +33,7 @@ Before adding a new SSH key to your account on {% data variables.location.produc
You can add an SSH key and use it for authentication, or commit signing, or both. If you want to use the same SSH key for both authentication and signing, you need to upload it twice.
After adding a new SSH authentication key to your account on {% data variables.location.product_location %}, you can reconfigure any local repositories to use SSH. For more information, see [AUTOTITLE](/get-started/getting-started-with-git/managing-remote-repositories#switching-remote-urls-from-https-to-ssh).
After adding a new SSH authentication key to your account on {% data variables.location.product_location %}, you can reconfigure any local repositories to use SSH. For more information, see [AUTOTITLE](/get-started/git-basics/managing-remote-repositories#switching-remote-urls-from-https-to-ssh).
{% data reusables.ssh.key-type-support %}

4
content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md
View File

@@ -108,7 +108,7 @@ For more information, see [AUTOTITLE](/actions/security-guides/automatic-token-a
## Authenticating with the command line
You can access repositories on {% data variables.product.github %} from the command line in two ways, HTTPS and SSH, and both have a different way of authenticating. The method of authenticating is determined based on whether you choose an HTTPS or SSH remote URL when you clone the repository. For more information about which way to access, see [AUTOTITLE](/get-started/getting-started-with-git/about-remote-repositories).
You can access repositories on {% data variables.product.github %} from the command line in two ways, HTTPS and SSH, and both have a different way of authenticating. The method of authenticating is determined based on whether you choose an HTTPS or SSH remote URL when you clone the repository. For more information about which way to access, see [AUTOTITLE](/get-started/git-basics/about-remote-repositories).
### HTTPS
@@ -116,7 +116,7 @@ You can work with all repositories on {% data variables.product.github %} over H
If you authenticate with {% data variables.product.prodname_cli %}, you can either authenticate with a {% data variables.product.pat_generic %} or via the web browser. For more information about authenticating with {% data variables.product.prodname_cli %}, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login).
If you authenticate without {% data variables.product.prodname_cli %}, you must authenticate with a {% data variables.product.pat_generic %}. {% data reusables.user-settings.password-authentication-deprecation %} Every time you use Git to authenticate with {% data variables.product.github %}, you'll be prompted to enter your credentials, unless you cache them with a [credential helper](/get-started/getting-started-with-git/caching-your-github-credentials-in-git).
If you authenticate without {% data variables.product.prodname_cli %}, you must authenticate with a {% data variables.product.pat_generic %}. {% data reusables.user-settings.password-authentication-deprecation %} Every time you use Git to authenticate with {% data variables.product.github %}, you'll be prompted to enter your credentials, unless you cache them with a [credential helper](/get-started/git-basics/caching-your-github-credentials-in-git).
### SSH

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

@@ -34,5 +34,5 @@ You can only use your password to log on to {% data variables.product.github %}
## Further reading
* [AUTOTITLE](/get-started/getting-started-with-git/caching-your-github-credentials-in-git)
* [AUTOTITLE](/get-started/git-basics/caching-your-github-credentials-in-git)
* [AUTOTITLE](/authentication/keeping-your-account-and-data-secure)

6
content/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens.md
View File

@@ -139,11 +139,11 @@ Username: YOUR-USERNAME
Password: YOUR-PERSONAL-ACCESS-TOKEN
```
{% data variables.product.pat_generic_caps %}s can only be used for HTTPS Git operations. If your repository uses an SSH remote URL, you will need to [switch the remote from SSH to HTTPS](/get-started/getting-started-with-git/managing-remote-repositories#switching-remote-urls-from-ssh-to-https).
{% data variables.product.pat_generic_caps %}s can only be used for HTTPS Git operations. If your repository uses an SSH remote URL, you will need to [switch the remote from SSH to HTTPS](/get-started/git-basics/managing-remote-repositories#switching-remote-urls-from-ssh-to-https).
If you are not prompted for your username and password, your credentials may be cached on your computer. You can [update your credentials in the Keychain](/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain) to replace your old password with the token.
If you are not prompted for your username and password, your credentials may be cached on your computer. You can [update your credentials in the Keychain](/get-started/git-basics/updating-credentials-from-the-macos-keychain) to replace your old password with the token.
Instead of manually entering your {% data variables.product.pat_generic %} for every HTTPS Git operation, you can cache your {% data variables.product.pat_generic %} with a Git client. Git will temporarily store your credentials in memory until an expiry interval has passed. You can also store the token in a plain text file that Git can read before every request. For more information, see [AUTOTITLE](/get-started/getting-started-with-git/caching-your-github-credentials-in-git).
Instead of manually entering your {% data variables.product.pat_generic %} for every HTTPS Git operation, you can cache your {% data variables.product.pat_generic %} with a Git client. Git will temporarily store your credentials in memory until an expiry interval has passed. You can also store the token in a plain text file that Git can read before every request. For more information, see [AUTOTITLE](/get-started/git-basics/caching-your-github-credentials-in-git).
## Further reading

2
content/authentication/troubleshooting-ssh/error-bad-file-number.md
View File

@@ -27,7 +27,7 @@ $ ssh -vT git@{% data variables.product.product_url %}
### Use HTTPS
Often, the simplest solution is to simply avoid SSH entirely. Most firewalls and proxies allow HTTPS traffic without issue. To take advantage of this, change [the remote URL](/get-started/getting-started-with-git/about-remote-repositories) you're using:
Often, the simplest solution is to simply avoid SSH entirely. Most firewalls and proxies allow HTTPS traffic without issue. To take advantage of this, change [the remote URL](/get-started/git-basics/about-remote-repositories) you're using:
```shell
$ git clone https://{% data variables.product.product_url %}/USERNAME/REPO-NAME.git

2
content/authentication/troubleshooting-ssh/error-permission-denied-publickey.md
View File

@@ -54,7 +54,7 @@ $ ssh -T GITHUB-USERNAME@{% data variables.product.product_url %}
> Permission denied (publickey).
```
If your connection failed and you're using a remote URL with your {% data variables.product.github %} username, you can [change the remote URL to use the "git" user](/get-started/getting-started-with-git/managing-remote-repositories).
If your connection failed and you're using a remote URL with your {% data variables.product.github %} username, you can [change the remote URL to use the "git" user](/get-started/git-basics/managing-remote-repositories).
You should verify your connection by typing:

4
content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md
View File

@@ -30,12 +30,12 @@ If you [configured your SSH passphrase with the macOS keychain](/authentication/
{% windows %}
If you lose your SSH key passphrase, there's no way to recover it. You'll need to [generate a brand new SSH keypair](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) or [switch to HTTPS cloning](/get-started/getting-started-with-git/about-remote-repositories#cloning-with-https-urls) so you can use a {% data variables.product.pat_generic %} instead.
If you lose your SSH key passphrase, there's no way to recover it. You'll need to [generate a brand new SSH keypair](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) or [switch to HTTPS cloning](/get-started/git-basics/about-remote-repositories#cloning-with-https-urls) so you can use a {% data variables.product.pat_generic %} instead.
{% endwindows %}
{% linux %}
If you lose your SSH key passphrase, there's no way to recover it. You'll need to [generate a brand new SSH keypair](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) or [switch to HTTPS cloning](/get-started/getting-started-with-git/about-remote-repositories#cloning-with-https-urls) so you can use a {% data variables.product.pat_generic %} instead.
If you lose your SSH key passphrase, there's no way to recover it. You'll need to [generate a brand new SSH keypair](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) or [switch to HTTPS cloning](/get-started/git-basics/about-remote-repositories#cloning-with-https-urls) so you can use a {% data variables.product.pat_generic %} instead.
{% endlinux %}

16
content/contributing/writing-for-github-docs/using-markdown-and-liquid-in-github-docs.md
View File

@@ -403,17 +403,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/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`
* `/en/get-started/git-basics/set-up-git`
* `/en/enterprise-cloud@latest/get-started/git-basics/set-up-git`
* `/en/enterprise-server@3.10/get-started/git-basics/set-up-git`
* `/en/enterprise-server@3.9/get-started/git-basics/set-up-git`
* `/en/enterprise-server@3.8/get-started/git-basics/set-up-git`
* `/en/enterprise-server@3.7/get-started/git-basics/set-up-git`
* `/en/enterprise-server@3.6/get-started/git-basics/set-up-git`
An article that is not available in {% data variables.product.prodname_ghe_server %} will have just one permalink:
* `/en/get-started/getting-started-with-git/set-up-git`
* `/en/get-started/git-basics/set-up-git`
> [!NOTE]
> If you are a content contributor, you don't need to worry about supported versions when adding a link to a document. Following the examples above, if you want to reference an article, you can just use its relative location: `/github/getting-started-with-github/set-up-git`.

2
content/desktop/adding-and-cloning-repositories/cloning-and-forking-repositories-from-github-desktop.md
View File

@@ -56,4 +56,4 @@ You can create an alias for a local repository to help differentiate between rep
## Further reading
* [About remote repositories](/get-started/getting-started-with-git/about-remote-repositories)
* [About remote repositories](/get-started/git-basics/about-remote-repositories)

2
content/desktop/installing-and-authenticating-to-github-desktop/about-connections-to-github-in-github-desktop.md
View File

@@ -16,7 +16,7 @@ shortTitle: About connections
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 {% data variables.product.pat_generic %}) 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 [AUTOTITLE](/get-started/getting-started-with-git/managing-remote-repositories).
{% 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 [AUTOTITLE](/get-started/git-basics/managing-remote-repositories).
## Further reading

2
content/desktop/overview/creating-your-first-repository-using-github-desktop.md
View File

@@ -50,7 +50,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.github %}, the README is the first thing they'll see as they learn about your project. For more information, see [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/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 [AUTOTITLE](/get-started/getting-started-with-git/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 [AUTOTITLE](/get-started/git-basics/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 [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository).
1. Click **Create repository**.

7
content/get-started/getting-started-with-git/about-remote-repositories.md → content/get-started/git-basics/about-remote-repositories.md
View File

@@ -10,6 +10,7 @@ redirect_from:
- /github/using-git/about-remote-repositories
- /github/getting-started-with-github/about-remote-repositories
- /github/getting-started-with-github/getting-started-with-git/about-remote-repositories
- /get-started/getting-started-with-git/about-remote-repositories
intro: 'GitHub''s collaborative approach to development depends on publishing commits from your local repository to {% data variables.product.github %} for other people to view, fetch, and update.'
versions:
fpt: '*'
@@ -38,7 +39,7 @@ git remote add origin <REMOTE_URL>
This associates the name `origin` with the `REMOTE_URL`.
You can use the command `git remote set-url` to [change a remote's URL](/get-started/getting-started-with-git/managing-remote-repositories).
You can use the command `git remote set-url` to [change a remote's URL](/get-started/git-basics/managing-remote-repositories).
## Choosing a URL for your remote repository
@@ -46,7 +47,7 @@ There are several ways to clone repositories available on {% data variables.prod
When you view a repository while signed in to your account, the URLs you can use to clone the project onto your computer are available below the repository details.
For information on setting or changing your remote URL, see [AUTOTITLE](/get-started/getting-started-with-git/managing-remote-repositories).
For information on setting or changing your remote URL, see [AUTOTITLE](/get-started/git-basics/managing-remote-repositories).
## Cloning with HTTPS URLs
@@ -57,7 +58,7 @@ When you `git clone`, `git fetch`, `git pull`, or `git push` to a private remote
{% data reusables.command_line.provide-an-access-token %}
> [!TIP]
> * You can use a credential helper so Git will remember your {% data variables.product.prodname_dotcom %} credentials every time it talks to {% data variables.product.prodname_dotcom %}. For more information, see [AUTOTITLE](/get-started/getting-started-with-git/caching-your-github-credentials-in-git).
> * You can use a credential helper so Git will remember your {% data variables.product.prodname_dotcom %} credentials every time it talks to {% data variables.product.prodname_dotcom %}. For more information, see [AUTOTITLE](/get-started/git-basics/caching-your-github-credentials-in-git).
> * To clone a repository without authenticating to {% data variables.product.github %} on the command line, you can use {% data variables.product.prodname_desktop %} to clone instead. For more information, see [AUTOTITLE](/desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop).
{% ifversion fpt or ghec %}If you'd rather use SSH but cannot connect over port 22, you might be able to use SSH over the HTTPS port. For more information, see [AUTOTITLE](/authentication/troubleshooting-ssh/using-ssh-over-the-https-port).{% endif %}

1
content/get-started/getting-started-with-git/associating-text-editors-with-git.md → content/get-started/git-basics/associating-text-editors-with-git.md
View File

@@ -9,6 +9,7 @@ redirect_from:
- /github/using-git/associating-text-editors-with-git
- /github/getting-started-with-github/associating-text-editors-with-git
- /github/getting-started-with-github/getting-started-with-git/associating-text-editors-with-git
- /get-started/getting-started-with-git/associating-text-editors-with-git
versions:
fpt: '*'
ghes: '*'

1
content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md → content/get-started/git-basics/caching-your-github-credentials-in-git.md
View File

@@ -7,6 +7,7 @@ redirect_from:
- /github/using-git/caching-your-github-credentials-in-git
- /github/getting-started-with-github/caching-your-github-credentials-in-git
- /github/getting-started-with-github/getting-started-with-git/caching-your-github-credentials-in-git
- /get-started/getting-started-with-git/caching-your-github-credentials-in-git
intro: 'If you''re [cloning {% data variables.product.github %} repositories using HTTPS](/github/getting-started-with-github/about-remote-repositories), we recommend you use {% data variables.product.prodname_cli %} or Git Credential Manager (GCM) to remember your credentials.'
versions:
fpt: '*'

1
content/get-started/getting-started-with-git/configuring-git-to-handle-line-endings.md → content/get-started/git-basics/configuring-git-to-handle-line-endings.md
View File

@@ -9,6 +9,7 @@ redirect_from:
- /github/using-git/configuring-git-to-handle-line-endings
- /github/getting-started-with-github/configuring-git-to-handle-line-endings
- /github/getting-started-with-github/getting-started-with-git/configuring-git-to-handle-line-endings
- /get-started/getting-started-with-git/configuring-git-to-handle-line-endings
versions:
fpt: '*'
ghes: '*'

1
content/get-started/getting-started-with-git/git-cheatsheet.md → content/get-started/git-basics/git-cheatsheet.md
View File

@@ -5,6 +5,7 @@ redirect_from:
- /github/getting-started-with-github/git-cheatsheet
- /github/getting-started-with-github/quickstart/git-cheatsheet
- /get-started/quickstart/git-cheatsheet
- /get-started/getting-started-with-git/git-cheatsheet
versions:
fpt: '*'
ghes: '*'

1
content/get-started/getting-started-with-git/git-workflows.md → content/get-started/git-basics/git-workflows.md
View File

@@ -7,6 +7,7 @@ redirect_from:
- /github/using-git/git-workflows
- /github/getting-started-with-github/git-workflows
- /github/getting-started-with-github/getting-started-with-git/git-workflows
- /get-started/getting-started-with-git/git-workflows
versions:
fpt: '*'
ghes: '*'

1
content/get-started/getting-started-with-git/ignoring-files.md → content/get-started/git-basics/ignoring-files.md
View File

@@ -7,6 +7,7 @@ redirect_from:
- /github/using-git/ignoring-files
- /github/getting-started-with-github/ignoring-files
- /github/getting-started-with-github/getting-started-with-git/ignoring-files
- /get-started/getting-started-with-git/ignoring-files
intro: 'You can configure Git to ignore files you don''t want to check in to {% data variables.product.github %}.'
versions:
fpt: '*'

3
content/get-started/getting-started-with-git/index.md → content/get-started/git-basics/index.md
View File

@@ -1,5 +1,5 @@
---
title: Getting started with Git
title: Git basics
intro: 'Set up Git, a distributed version control system, to manage your {% data variables.product.github %} repositories from your computer.'
redirect_from:
- /articles/getting-started-with-git-and-github
@@ -7,6 +7,7 @@ redirect_from:
- /github/using-git/learning-about-git
- /articles/learning-about-git
- /github/getting-started-with-github/getting-started-with-git
- /get-started/getting-started-with-git
versions:
fpt: '*'
ghes: '*'

11
content/get-started/getting-started-with-git/managing-remote-repositories.md → content/get-started/git-basics/managing-remote-repositories.md
View File

@@ -18,6 +18,7 @@ redirect_from:
- /github/using-git/managing-remote-repositories
- /github/getting-started-with-github/managing-remote-repositories
- /github/getting-started-with-github/getting-started-with-git/managing-remote-repositories
- /get-started/getting-started-with-git/managing-remote-repositories
versions:
fpt: '*'
ghes: '*'
@@ -50,7 +51,7 @@ $ git remote -v
> origin https://{% data variables.product.product_url %}/OWNER/REPOSITORY.git (push)
```
For more information on which URL to use, see [AUTOTITLE](/get-started/getting-started-with-git/about-remote-repositories).
For more information on which URL to use, see [AUTOTITLE](/get-started/git-basics/about-remote-repositories).
### Troubleshooting: Remote origin already exists
@@ -71,7 +72,7 @@ To fix this, you can:
The `git remote set-url` command changes an existing remote repository URL.
> [!TIP]
> For information on the difference between HTTPS and SSH URLs, see [AUTOTITLE](/get-started/getting-started-with-git/about-remote-repositories).
> For information on the difference between HTTPS and SSH URLs, see [AUTOTITLE](/get-started/git-basics/about-remote-repositories).
The `git remote set-url` command takes two arguments:
@@ -118,7 +119,7 @@ The `git remote set-url` command takes two arguments:
The next time you `git fetch`, `git pull`, or `git push` to the remote repository, you'll be asked for your GitHub username and password. {% data reusables.user-settings.password-authentication-deprecation %}
You can [use a credential helper](/get-started/getting-started-with-git/caching-your-github-credentials-in-git) so Git will remember your GitHub username and {% data variables.product.pat_generic %} every time it talks to GitHub.
You can [use a credential helper](/get-started/git-basics/caching-your-github-credentials-in-git) so Git will remember your GitHub username and {% data variables.product.pat_generic %} every time it talks to GitHub.
### Switching remote URLs from HTTPS to SSH
@@ -168,7 +169,7 @@ The `git remote rename` command takes two arguments:
### Example of renaming a remote repository
These examples assume you're [cloning using HTTPS](/get-started/getting-started-with-git/about-remote-repositories#cloning-with-https-urls), which is recommended.
These examples assume you're [cloning using HTTPS](/get-started/git-basics/about-remote-repositories#cloning-with-https-urls), which is recommended.
```shell
$ git remote -v
@@ -213,7 +214,7 @@ Removing the remote URL from your repository only unlinks the local and remote r
### Example of removing a remote repository
These examples assume you're [cloning using HTTPS](/get-started/getting-started-with-git/about-remote-repositories#cloning-with-https-urls), which is recommended.
These examples assume you're [cloning using HTTPS](/get-started/git-basics/about-remote-repositories#cloning-with-https-urls), which is recommended.
```shell
$ git remote -v

7
content/get-started/getting-started-with-git/set-up-git.md → content/get-started/git-basics/set-up-git.md
View File

@@ -13,6 +13,7 @@ redirect_from:
- /github/getting-started-with-github/set-up-git
- /github/getting-started-with-github/quickstart/set-up-git
- /get-started/quickstart/set-up-git
- /get-started/getting-started-with-git/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: '*'
@@ -48,7 +49,7 @@ If you do not need to work with files locally, {% data variables.product.github
> 1. Install a terminal emulator such as Termux from the Google Play Store on your Chrome OS device.
> 1. From the terminal emulator that you installed, install Git. For example, in Termux, enter `apt install git` and then type `y` when prompted.
1. [Set your username in Git](/get-started/getting-started-with-git/setting-your-username-in-git).
1. [Set your username in Git](/get-started/git-basics/setting-your-username-in-git).
1. [Set your commit email address in Git](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address).
## Authenticating with {% data variables.product.github %} from Git
@@ -60,11 +61,11 @@ When you connect to a {% data variables.product.github %} repository from Git, y
### Connecting over HTTPS (recommended)
If you clone with HTTPS, you can cache your {% data variables.product.prodname_dotcom %} credentials in Git using a credential helper. For more information, see [AUTOTITLE](/get-started/getting-started-with-git/about-remote-repositories#cloning-with-https-urls) and [AUTOTITLE](/get-started/getting-started-with-git/caching-your-github-credentials-in-git).
If you clone with HTTPS, you can cache your {% data variables.product.prodname_dotcom %} credentials in Git using a credential helper. For more information, see [AUTOTITLE](/get-started/git-basics/about-remote-repositories#cloning-with-https-urls) and [AUTOTITLE](/get-started/git-basics/caching-your-github-credentials-in-git).
### Connecting over SSH
If you clone with SSH, you must generate SSH keys on each computer you use to push or pull from {% data variables.product.github %}. For more information, see [AUTOTITLE](/get-started/getting-started-with-git/about-remote-repositories#cloning-with-ssh-urls) and [AUTOTITLE](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent).
If you clone with SSH, you must generate SSH keys on each computer you use to push or pull from {% data variables.product.github %}. For more information, see [AUTOTITLE](/get-started/git-basics/about-remote-repositories#cloning-with-ssh-urls) and [AUTOTITLE](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent).
## Next steps

1
content/get-started/getting-started-with-git/setting-your-username-in-git.md → content/get-started/git-basics/setting-your-username-in-git.md
View File

@@ -6,6 +6,7 @@ redirect_from:
- /github/using-git/setting-your-username-in-git
- /github/getting-started-with-github/setting-your-username-in-git
- /github/getting-started-with-github/getting-started-with-git/setting-your-username-in-git
- /get-started/getting-started-with-git/setting-your-username-in-git
versions:
fpt: '*'
ghes: '*'

5
content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md → content/get-started/git-basics/updating-credentials-from-the-macos-keychain.md
View File

@@ -7,6 +7,7 @@ redirect_from:
- /github/using-git/updating-credentials-from-the-macos-keychain
- /github/getting-started-with-github/updating-credentials-from-the-macos-keychain
- /github/getting-started-with-github/getting-started-with-git/updating-credentials-from-the-macos-keychain
- /get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain
versions:
fpt: '*'
ghes: '*'
@@ -17,7 +18,7 @@ shortTitle: macOS Keychain credentials
> [!NOTE]
> Updating credentials from the macOS Keychain only applies to users who manually configured a {% data variables.product.pat_generic %} using the `osxkeychain` helper that is built-in to macOS.
>
> We recommend you either [configure SSH](/authentication/connecting-to-github-with-ssh) or upgrade to the [Git Credential Manager](/get-started/getting-started-with-git/caching-your-github-credentials-in-git) (GCM) instead. GCM can manage authentication on your behalf (no more manual {% data variables.product.pat_generic %}s) including 2FA (two-factor auth).
> We recommend you either [configure SSH](/authentication/connecting-to-github-with-ssh) or upgrade to the [Git Credential Manager](/get-started/git-basics/caching-your-github-credentials-in-git) (GCM) instead. GCM can manage authentication on your behalf (no more manual {% data variables.product.pat_generic %}s) including 2FA (two-factor auth).
{% data reusables.user-settings.password-authentication-deprecation %}
@@ -51,4 +52,4 @@ If it's successful, nothing will print out. To test that it works, try and clone
## Further reading
* [AUTOTITLE](/get-started/getting-started-with-git/caching-your-github-credentials-in-git)
* [AUTOTITLE](/get-started/git-basics/caching-your-github-credentials-in-git)

5
content/get-started/getting-started-with-git/why-is-git-always-asking-for-my-password.md → content/get-started/git-basics/why-is-git-always-asking-for-my-password.md
View File

@@ -6,6 +6,7 @@ redirect_from:
- /github/using-git/why-is-git-always-asking-for-my-password
- /github/getting-started-with-github/why-is-git-always-asking-for-my-password
- /github/getting-started-with-github/getting-started-with-git/why-is-git-always-asking-for-my-password
- /get-started/getting-started-with-git/why-is-git-always-asking-for-my-password
versions:
fpt: '*'
ghes: '*'
@@ -16,10 +17,10 @@ Using an HTTPS remote URL has some advantages compared with using SSH. It's easi
{% data reusables.user-settings.password-authentication-deprecation %}
You can avoid being prompted for your password by configuring Git to [cache your credentials](/get-started/getting-started-with-git/caching-your-github-credentials-in-git) for you. Once you've configured credential caching, Git automatically uses your cached {% data variables.product.pat_generic %} when you pull or push a repository using HTTPS.
You can avoid being prompted for your password by configuring Git to [cache your credentials](/get-started/git-basics/caching-your-github-credentials-in-git) for you. Once you've configured credential caching, Git automatically uses your cached {% data variables.product.pat_generic %} when you pull or push a repository using HTTPS.
## Further reading
* [AUTOTITLE](/get-started/getting-started-with-git/about-remote-repositories)
* [AUTOTITLE](/get-started/git-basics/about-remote-repositories)
* [AUTOTITLE](/authentication/keeping-your-account-and-data-secure/about-authentication-to-github)
* [AUTOTITLE](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent)

4
content/get-started/index.md
View File

@@ -35,7 +35,7 @@ featuredLinks:
popular:
- /get-started/start-your-journey/creating-an-account-on-github
- /get-started/start-your-journey/hello-world
- /get-started/getting-started-with-git/set-up-git
- /get-started/git-basics/set-up-git
- /get-started/using-github-docs/about-versions-of-github-docs
- /get-started/learning-about-github/github-glossary
- /get-started/accessibility/keyboard-shortcuts
@@ -57,7 +57,7 @@ children:
- /accessibility
- /writing-on-github
- /exploring-projects-on-github
- /getting-started-with-git
- /git-basics
- /using-git
- /working-with-subversion-on-github
- /exploring-integrations

4
content/get-started/onboarding/getting-started-with-your-github-account.md
View File

@@ -68,11 +68,11 @@ To best use {% data variables.product.github %}, you'll need to set up Git. Git
### 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/getting-started-with-git/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/git-basics/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).
Once you install Git, you can connect to {% data variables.product.github %} repositories from your local computer, whether your own repository or another user's fork. When you connect to a repository on {% data variables.location.product_location %} from Git, you'll need to authenticate with {% data variables.product.github %} using either HTTPS or SSH. For more information, see [AUTOTITLE](/get-started/getting-started-with-git/about-remote-repositories).
Once you install Git, you can connect to {% data variables.product.github %} repositories from your local computer, whether your own repository or another user's fork. When you connect to a repository on {% data variables.location.product_location %} from Git, you'll need to authenticate with {% data variables.product.github %} using either HTTPS or SSH. For more information, see [AUTOTITLE](/get-started/git-basics/about-remote-repositories).
### 3. Choosing how to interact with {% data variables.product.github %}

2
content/get-started/using-git/about-git-rebase.md
View File

@@ -64,7 +64,7 @@ There are six commands available while rebasing:
## An example of using `git rebase`
No matter which command you use, Git will launch [your default text editor](/get-started/getting-started-with-git/associating-text-editors-with-git) and open a file that details the commits in the range you've chosen. That file looks something like this:
No matter which command you use, Git will launch [your default text editor](/get-started/git-basics/associating-text-editors-with-git) and open a file that details the commits in the range you've chosen. That file looks something like this:
```text
pick 1fc6c95 Patch A

2
content/get-started/using-git/about-git-subtree-merges.md
View File

@@ -102,7 +102,7 @@ The best way to explain subtree merges is to show by example. We will:
Although we've only added one subproject, any number of subprojects can be incorporated into a Git repository.
> [!TIP]
> If you create a fresh clone of the repository in the future, the remotes you've added will not be created for you. You will have to add them again using [the `git remote add` command](/get-started/getting-started-with-git/managing-remote-repositories).
> If you create a fresh clone of the repository in the future, the remotes you've added will not be created for you. You will have to add them again using [the `git remote add` command](/get-started/git-basics/managing-remote-repositories).
## Synchronizing with updates and changes

6
content/get-started/using-git/getting-changes-from-a-remote-repository.md
View File

@@ -15,7 +15,7 @@ shortTitle: Get changes from a remote
---
## Options for getting changes
These commands are very useful when interacting with [a remote repository](/get-started/getting-started-with-git/about-remote-repositories). `clone` and `fetch` download remote code from a repository's remote URL to your local computer, `merge` is used to merge different people's work together with yours, and `pull` is a combination of `fetch` and `merge`.
These commands are very useful when interacting with [a remote repository](/get-started/git-basics/about-remote-repositories). `clone` and `fetch` download remote code from a repository's remote URL to your local computer, `merge` is used to merge different people's work together with yours, and `pull` is a combination of `fetch` and `merge`.
## Cloning a repository
@@ -26,7 +26,7 @@ $ git clone https://{% data variables.product.product_url %}/USERNAME/REPOSITORY
# Clones a repository to your computer
```
You can choose from [several different URLs](/get-started/getting-started-with-git/about-remote-repositories) when cloning a repository. While logged in to {% data variables.product.prodname_dotcom %}, these URLs are available on the main page of the repository when you click **{% octicon "code" aria-hidden="true" %} Code**.
You can choose from [several different URLs](/get-started/git-basics/about-remote-repositories) when cloning a repository. While logged in to {% data variables.product.prodname_dotcom %}, these URLs are available on the main page of the repository when you click **{% octicon "code" aria-hidden="true" %} Code**.
![Screenshot of the main page of a repository. A green "Code" button is outlined in orange and expanded to show the HTTPS URL for the repository.](/assets/images/help/repository/remotes-url-global-nav-update.png)
@@ -52,7 +52,7 @@ $ git fetch REMOTE-NAME
# Fetches updates made to a remote repository
```
Otherwise, you can always add a new remote and then fetch. For more information, see [AUTOTITLE](/get-started/getting-started-with-git/managing-remote-repositories).
Otherwise, you can always add a new remote and then fetch. For more information, see [AUTOTITLE](/get-started/git-basics/managing-remote-repositories).
## Merging changes into your local branch

4
content/get-started/using-git/pushing-commits-to-a-remote-repository.md
View File

@@ -128,7 +128,7 @@ For more information on working with forks, see [AUTOTITLE](/pull-requests/colla
* [The "Remotes" chapter from the "Pro Git" book](https://git-scm.com/book/en/v2/Git-Basics-Working-with-Remotes)
* [`git remote` main page](https://git-scm.com/docs/git-remote.html)
* [AUTOTITLE](/get-started/getting-started-with-git/git-cheatsheet)
* [AUTOTITLE](/get-started/getting-started-with-git/git-workflows)
* [AUTOTITLE](/get-started/git-basics/git-cheatsheet)
* [AUTOTITLE](/get-started/git-basics/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 %}

2
content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md
View File

@@ -66,7 +66,7 @@ If you create a new clone of the repository, you won't lose any of your Git hist
![Screenshot of the "Quick Setup" header in a repository. Next to the remote URL, an icon of two overlapping squares is outlined in orange.](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png)
> [!TIP]
> For information on the difference between HTTPS and SSH URLs, see [AUTOTITLE](/get-started/getting-started-with-git/about-remote-repositories).
> For information on the difference between HTTPS and SSH URLs, see [AUTOTITLE](/get-started/git-basics/about-remote-repositories).
1. Add a new remote name with the URL you copied for your repository. For example, `origin` or `upstream` are two common choices.

2
content/get-started/using-git/troubleshooting-the-2-gb-push-limit.md
View File

@@ -22,7 +22,7 @@ You can either split up your push into smaller parts, or delete the Git history
You can avoid hitting the limit by breaking your push into smaller parts, each of which should be under 2 GB in size. If a branch is within this size limit, you can push it all at once. However, if a branch is larger than 2 GB, you'll need to split the push into even smaller portions and push only a few commits at a time.
1. If you haven't configured the remote yet, add the repository as a new remote. For more information, see [AUTOTITLE](/get-started/getting-started-with-git/managing-remote-repositories#adding-a-remote-repository).
1. If you haven't configured the remote yet, add the repository as a new remote. For more information, see [AUTOTITLE](/get-started/git-basics/managing-remote-repositories#adding-a-remote-repository).
1. To find suitable commits spread out along the history of the main branch in your local repository, run the following command:
```shell

4
content/get-started/using-github/connecting-to-github.md
View File

@@ -56,7 +56,7 @@ If you haven't worked with a {% data variables.product.github %} repository from
There are several tools you can use to connect to {% data variables.product.github %} from your desktop. These tools allow you to authenticate to {% data variables.product.github %}, clone a repository, track your changes, and push the changes to {% data variables.product.github %}.
* 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.github %}, 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 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.github %}, such as creating a pull request or forking a repository. For more information, see [AUTOTITLE](/get-started/git-basics/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.github %} all from one place. You can also install an extension to work directly with pull requests and issues on {% data variables.product.github %}. To get started, see [Download {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/download).
@@ -77,7 +77,7 @@ For more information about how to authenticate to {% data variables.product.gith
| {% 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.github %}. 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/getting-started-with-git/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/git-basics/set-up-git) and [AUTOTITLE](/github-cli/github-cli/about-github-cli). | Desktop |
| **{% ifversion fpt or ghec %}{% data variables.product.github %}{% else %}{% data variables.product.prodname_ghe_server %}{% endif %} API** | You want to automate common tasks such as backing up your data, or create integrations that extend {% data variables.product.github %}. For more information, see [AUTOTITLE](/rest/about-the-rest-api/comparing-githubs-rest-api-and-graphql-api). | Browser or desktop |
## Further reading

4
content/index.md
View File

@@ -2,7 +2,7 @@
title: '{% data variables.product.github %}{% ifversion fpt or ghec%}.com{% endif %} Help Documentation'
featuredLinks:
gettingStarted:
- /get-started/getting-started-with-git/set-up-git
- /get-started/git-basics/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
@@ -10,7 +10,7 @@ featuredLinks:
- /pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests
- /authentication
- /copilot/using-github-copilot/getting-code-suggestions-in-your-ide-with-github-copilot
- /get-started/getting-started-with-git/managing-remote-repositories
- /get-started/git-basics/managing-remote-repositories
- /pages
redirect_from:
- /github

6
content/migrations/importing-source-code/using-the-command-line-to-import-source-code/adding-locally-hosted-code-to-github.md
View File

@@ -110,7 +110,7 @@ Before you can add your local repository to {% data variables.product.prodname_d
git remote add origin REMOTE-URL
```
For more information, see [AUTOTITLE](/get-started/getting-started-with-git/managing-remote-repositories).
For more information, see [AUTOTITLE](/get-started/git-basics/managing-remote-repositories).
1. To verify that you set the remote URL correctly, run the following command.
```shell
@@ -143,7 +143,7 @@ Before you can add your local repository to {% data variables.product.prodname_d
git remote add origin REMOTE-URL
```
For more information, see [AUTOTITLE](/get-started/getting-started-with-git/managing-remote-repositories).
For more information, see [AUTOTITLE](/get-started/git-basics/managing-remote-repositories).
1. To verify that you set the remote URL correctly, run the following command.
```shell
@@ -176,7 +176,7 @@ Before you can add your local repository to {% data variables.product.prodname_d
git remote add origin REMOTE-URL
```
For more information, see [AUTOTITLE](/get-started/getting-started-with-git/managing-remote-repositories).
For more information, see [AUTOTITLE](/get-started/git-basics/managing-remote-repositories).
1. To verify that you set the remote URL correctly, run the following command.
```shell

2
content/organizations/managing-organization-settings/renaming-an-organization.md
View File

@@ -24,7 +24,7 @@ After changing your organization's name, your old organization name becomes avai
### Changes that occur automatically
* {% data variables.product.prodname_dotcom %} automatically redirects references to your repositories. Web links to your organization's existing **repositories** will continue to work. This can take a few minutes to complete after you initiate the change.
* You can continue pushing your local repositories to the old remote tracking URL without updating it. However, we recommend you update all existing remote repository URLs after changing your organization name. Because your old organization name is available for use by anyone else after you change it, the new organization owner can create repositories that override the redirect entries to your repository. For more information, see [AUTOTITLE](/get-started/getting-started-with-git/managing-remote-repositories).
* You can continue pushing your local repositories to the old remote tracking URL without updating it. However, we recommend you update all existing remote repository URLs after changing your organization name. Because your old organization name is available for use by anyone else after you change it, the new organization owner can create repositories that override the redirect entries to your repository. For more information, see [AUTOTITLE](/get-started/git-basics/managing-remote-repositories).
* Previous Git commits will also be correctly attributed to users within your organization.{% ifversion fpt or ghec %}
* {% data reusables.accounts.rename-account-repo-namespace-retirement %}{% endif %}
* {% data reusables.package_registry.rename-account-namespace-retirement %}

2
content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md
View File

@@ -19,7 +19,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/getting-started-with-git/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/git-basics/set-up-git).
{% data reusables.pages.recommend-bundler %}

4
content/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo.md
View File

@@ -44,7 +44,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/getting-started-with-git/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/git-basics/set-up-git).
## Forking a repository
@@ -219,7 +219,7 @@ 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.
* 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).
* For more information about cloning the fork and syncing the changes in a forked repository from your computer, see [AUTOTITLE](/get-started/git-basics/set-up-git).
* 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 %}

2
content/repositories/creating-and-managing-repositories/creating-a-new-repository.md
View File

@@ -35,7 +35,7 @@ topics:
{% data reusables.repositories.choose-repo-visibility %}
1. If you're not using a template, there are a number of optional items you can pre-populate your repository with. If you're importing an existing repository to {% data variables.product.github %}, don't choose any of these options, as you may introduce a merge conflict. You can add or create new files using the user interface or choose to add new files using the command line later. For more information, see [AUTOTITLE](/migrations/importing-source-code/using-the-command-line-to-import-source-code/importing-an-external-git-repository-using-the-command-line), [AUTOTITLE](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository#adding-a-file-to-a-repository-using-the-command-line), and [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts).
* You can create a README, which is a document describing your project. For more information, see [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes).
* You can create a _.gitignore_ file, which is a set of ignore rules. For more information, see [AUTOTITLE](/get-started/getting-started-with-git/ignoring-files).{% ifversion fpt or ghec %}
* You can create a _.gitignore_ file, which is a set of ignore rules. For more information, see [AUTOTITLE](/get-started/git-basics/ignoring-files).{% ifversion fpt or ghec %}
* You can choose to add a software license for your project. For more information, see [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository).{% endif %}
{% data reusables.repositories.select-marketplace-apps %}
{%- ifversion custom-properties-on-create %}

2
content/repositories/creating-and-managing-repositories/quickstart-for-repositories.md
View File

@@ -118,7 +118,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/getting-started-with-git/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/git-basics/set-up-git).
{% endwebui %}

2
content/repositories/creating-and-managing-repositories/renaming-a-repository.md
View File

@@ -27,7 +27,7 @@ In addition to redirecting web traffic, all `git clone`, `git fetch`, or `git pu
git remote set-url origin NEW_URL
```
For more information, see [AUTOTITLE](/get-started/getting-started-with-git/managing-remote-repositories).
For more information, see [AUTOTITLE](/get-started/git-basics/managing-remote-repositories).
{% ifversion fpt or ghec %}

2
content/repositories/creating-and-managing-repositories/transferring-a-repository.md
View File

@@ -70,7 +70,7 @@ When you transfer a repository, its issues, pull requests, wiki, stars, and watc
* Sponsors who have access to the repository through a sponsorship tier may be affected. See [AUTOTITLE](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers#adding-a-repository-to-a-sponsorship-tier).{% endif %}
* Packages associated with the repository may be transferred, or may lose their link to the repository, depending on the registry they belong to. See [AUTOTITLE](/packages/learn-github-packages/about-permissions-for-github-packages#about-repository-transfers).
See [AUTOTITLE](/get-started/getting-started-with-git/managing-remote-repositories).
See [AUTOTITLE](/get-started/git-basics/managing-remote-repositories).
### Repository transfers and organizations

6
content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md
View File

@@ -83,11 +83,11 @@ To access {% data variables.product.prodname_dotcom %}, you must authenticate wi
When prompted for a username and password, make sure you use an account that has access to the repository.
> [!TIP]
> If you don't want to enter your credentials every time you interact with the remote repository, you can turn on [credential caching](/get-started/getting-started-with-git/caching-your-github-credentials-in-git). If you are already using credential caching, please make sure that your computer has the correct credentials cached. Incorrect or out of date credentials will cause authentication to fail.
> If you don't want to enter your credentials every time you interact with the remote repository, you can turn on [credential caching](/get-started/git-basics/caching-your-github-credentials-in-git). If you are already using credential caching, please make sure that your computer has the correct credentials cached. Incorrect or out of date credentials will cause authentication to fail.
### Use SSH instead
If you've previously set up SSH keys, you can use the SSH clone URL instead of HTTPS. For more information, see [AUTOTITLE](/get-started/getting-started-with-git/about-remote-repositories).
If you've previously set up SSH keys, you can use the SSH clone URL instead of HTTPS. For more information, see [AUTOTITLE](/get-started/git-basics/about-remote-repositories).
## Error: Repository not found
@@ -99,7 +99,7 @@ Typos happen. If you try to clone `git@{% data variables.product.product_url %}:
To avoid this error, when cloning, always copy and paste the clone URL from the repository's page. For more information, see [AUTOTITLE](/repositories/creating-and-managing-repositories/cloning-a-repository).
To update the remote on an existing repository, see [AUTOTITLE](/get-started/getting-started-with-git/managing-remote-repositories).
To update the remote on an existing repository, see [AUTOTITLE](/get-started/git-basics/managing-remote-repositories).
### Checking your permissions

2
content/rest/gitignore/gitignore.md
View File

@@ -18,6 +18,6 @@ autogenerated: rest
## About gitignore
When you create a new repository on {% data variables.product.github %} via the API, you can specify a [.gitignore template](/get-started/getting-started-with-git/ignoring-files) to apply to the repository upon creation. You can use the REST API to get .gitignore templates from the {% data variables.product.github %} [.gitignore repository](https://github.com/github/gitignore).
When you create a new repository on {% data variables.product.github %} via the API, you can specify a [.gitignore template](/get-started/git-basics/ignoring-files) to apply to the repository upon creation. You can use the REST API to get .gitignore templates from the {% data variables.product.github %} [.gitignore repository](https://github.com/github/gitignore).
<!-- Content after this section is automatically generated -->