You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: git-guides/git-pull.md
+2-3
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@
4
4
5
5
Without `git pull`, (or the effect of it,) your local branch wouldn't have any of the updates that are present on the remote.
6
6
7
-
###What Does `git pull` Do?
7
+
## What Does `git pull` Do?
8
8
9
9
```sh
10
10
git pull
@@ -20,7 +20,7 @@ git pull
20
20
21
21
However, you may want to use `git fetch` instead. One reason to do this may be that you expect conflicts. Conflicts can occur in this way if you have new local commits and new commits on the remote. Just like a merge conflict that would happen between two different branches, these two different lines of history could contain changes to the same parts of the same file. If you first operate `git fetch`, the merge won't be initiated, and you won't be prompted to solve the conflict. This gives you the flexibility to resolve the conflict later without the need for network connectivity.
22
22
23
-
Another reason you may want to run `git fetch` is to update to all remote tracking branches before losing network connectivity. If you run `git fetch`, and then later try to run `git pull` without any network connectivity, the `git fetch` portion of the `git pull` operation will fail.
23
+
Another reason you may want to run `git fetch` is to update to all remote tracking branches before losing network connectivity. If you run `git fetch`, and then later try to run `git pull` without any network connectivity, the `git fetch` portion of the `git pull` operation will fail.
24
24
25
25
If you do use `git fetch` instead of `git pull`, make sure you remember to `git merge`. Merging the remote tracking branch into your own branch ensures you will be working with any updates or changes.
26
26
@@ -90,4 +90,3 @@ Using `git pull --rebase` does not affect the integrity of the changes or the co
90
90
-`git push`: Uploads all local branch commits to the remote.
91
91
-`git log`: Browse and inspect the evolution of project files.
92
92
-`git remote -v`: Show the associated remote repositories and their stored name, like `origin`.
Copy file name to clipboardExpand all lines: git-guides/install-git.md
+5-5
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ Note: [`git-scm`](https://git-scm.com/download/win) is a popular and recommended
29
29
## Install Git on Windows through Visual Studio Code
30
30
31
31
GitHub integration is provided through the [GitHub Pull Requests and Issues extension](https://marketplace.visualstudio.com/items?itemName=GitHub.vscode-pull-request-github).
32
-
To get started with the GitHub in VS Code, you'll need to create an account and install the GitHub Pull Requests and Issues extension.
32
+
To get started with the GitHub in VS Code, you'll need to create an account and install the GitHub Pull Requests and Issues extension.
33
33
Once you've installed the [GitHub Pull Requests and Issues extension](https://marketplace.visualstudio.com/items?itemName=GitHub.vscode-pull-request-github), you'll need to sign in. Follow the prompts to authenticate with GitHub and return to VS Code.
34
34
35
35
@@ -44,15 +44,15 @@ Note: You can perform actions like, you can search for and clone a repository fr
44
44
45
45
Most versions of MacOS will already have `Git` installed, and you can activate it through the terminal with `git version`. However, if you don't have Git installed for whatever reason, you can install the latest version of Git using one of several popular methods as listed below:
46
46
47
-
####Install Git From an Installer
47
+
### Install Git From an Installer
48
48
49
49
1. Navigate to the latest [macOS Git Installer](https://sourceforge.net/projects/git-osx-installer/files/git-2.23.0-intel-universal-mavericks.dmg/download?use_mirror=autoselect) and download the latest version.
50
50
2. Once the installer has started, follow the instructions as provided until the installation is complete.
51
51
3. Open the command prompt "terminal" and type `git version` to verify Git was installed.
52
52
53
53
Note: [`git-scm`](https://git-scm.com/download/mac) is a popular and recommended resource for downloading Git on a Mac. The advantage of downloading Git from `git-scm` is that your download automatically starts with the latest version of Git. The download source is the same [macOS Git Installer](https://sourceforge.net/projects/git-osx-installer/files/git-2.23.0-intel-universal-mavericks.dmg/download?use_mirror=autoselect) as referenced in the steps above.
54
54
55
-
####Install Git from Homebrew
55
+
### Install Git from Homebrew
56
56
57
57
[Homebrew](https://brew.sh/) is a popular package manager for macOS. If you already have Homebrew installed, you can follow the below steps to install Git:
58
58
@@ -66,14 +66,14 @@ Fun fact: Git was originally developed to version the Linux operating system! So
66
66
67
67
You can install `Git` on Linux through the package management tool that comes with your distribution.
68
68
69
-
####Debian/Ubuntu
69
+
### Debian/Ubuntu
70
70
71
71
1. Git packages are available using `apt`.
72
72
2. It's a good idea to make sure you're running the latest version. To do so, Navigate to your command prompt shell and run the following command to make sure everything is up-to-date: `sudo apt-get update`.
73
73
3. To install Git, run the following command: `sudo apt-get install git-all`.
74
74
4. Once the command output has been completed, you can verify the installation by typing: `git version`.
75
75
76
-
####Fedora
76
+
### Fedora
77
77
78
78
1. Git packages are available using `dnf`.
79
79
2. To install Git, navigate to your command prompt shell and run the following command: `sudo dnf install git-all`.
0 commit comments