Merge branch 'docs-update-start-using-git.md' into 'master'
Update doc/gitlab-basics/start-using-git.md See merge request gitlab-org/gitlab-ce!31793
This commit is contained in:
commit
9940846a4e
|
@ -63,8 +63,8 @@ git config --global user.email
|
|||
|
||||
You'll need to do this only once, since you are using the `--global` option. It tells
|
||||
Git to always use this information for anything you do on that system. If you want
|
||||
to override this with a different username or email address for specific projects,
|
||||
you can run the command without the `--global` option when you’re in that project.
|
||||
to override this with a different username or email address for specific projects or repositories,
|
||||
you can run the command without the `--global` option when you’re in that project, and that will default to `--local`. You can read more on how Git manages configurations in the [Git Config](https://git-scm.com/book/en/v2/Customizing-Git-Git-Configuration) documentation.
|
||||
|
||||
## Check your information
|
||||
|
||||
|
@ -102,8 +102,7 @@ files to your local computer, automatically preserving the Git connection with t
|
|||
remote repository.
|
||||
|
||||
You can either clone it via HTTPS or [SSH](../ssh/README.md). If you chose to clone
|
||||
it via HTTPS, you'll have to enter your credentials every time you pull and push.
|
||||
With SSH, you enter your credentials only once.
|
||||
it via HTTPS, you'll have to enter your credentials every time you pull and push. You can read more about credential storage in the [Git Credentials documentation](https://git-scm.com/book/en/v2/Git-Tools-Credential-Storage). With SSH, you enter your credentials only once.
|
||||
|
||||
You can find both paths (HTTPS and SSH) by navigating to your project's landing page
|
||||
and clicking **Clone**. GitLab will prompt you with both paths, from which you can copy
|
||||
|
@ -152,13 +151,15 @@ to get the main branch code, or the branch name of the branch you are currently
|
|||
in.
|
||||
|
||||
```bash
|
||||
git pull REMOTE <name-of-branch>
|
||||
git pull <REMOTE> <name-of-branch>
|
||||
```
|
||||
|
||||
When you first clone a repository, REMOTE is typically `origin`. This is where the
|
||||
When you clone a repository, `REMOTE` is typically `origin`. This is where the
|
||||
repository was cloned from, and it indicates the SSH or HTTPS URL of the repository
|
||||
on the remote server. `<name-of-branch>` is usually `master`, but it may be any existing
|
||||
branch.
|
||||
branch. You can create additional named remotes and branches as necessary.
|
||||
|
||||
You can learn more on how Git manages remote repositories in the [Git Remote documentation](https://git-scm.com/book/en/v2/Git-Basics-Working-with-Remotes).
|
||||
|
||||
### View your remote repositories
|
||||
|
||||
|
@ -168,6 +169,8 @@ To view your remote repositories, type:
|
|||
git remote -v
|
||||
```
|
||||
|
||||
The `-v` flag stands for verbose.
|
||||
|
||||
### Add a remote repository
|
||||
|
||||
To add a link to a remote repository:
|
||||
|
@ -186,7 +189,7 @@ following (spaces won't be recognized in the branch name, so you will need to us
|
|||
hyphen or underscore):
|
||||
|
||||
```bash
|
||||
git checkout -b <name-of-branch>>
|
||||
git checkout -b <name-of-branch>
|
||||
```
|
||||
|
||||
### Work on an existing branch
|
||||
|
@ -238,7 +241,7 @@ git commit -m "COMMENT TO DESCRIBE THE INTENTION OF THE COMMIT"
|
|||
```
|
||||
|
||||
NOTE: **Note:**
|
||||
The `.` character typically means _all_ in Git.
|
||||
The `.` character means _all file changes in the current directory and all subdirectories_.
|
||||
|
||||
### Send changes to GitLab.com
|
||||
|
||||
|
|
Loading…
Reference in New Issue