@matheusbsbs / matheus-bagliano / commits / f4d7bccdb4
Fork 0

gitfaq: fetching and pulling a repository

Add an issue in 'Common Issues' section which addresses the confusion between performing a 'fetch' and a 'pull'. Helped-by: Elijah Newren <newren@gmail.com> Signed-off-by: Shourya Shukla <shouryashukla.oo@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>

Shourya Shukla committed May 6, 2020 at 22:41 UTC f4d7bccdb40b33792b6c22f60bbed92eef8aecf8
1 file changed +8
Documentation/gitfaq.txt
+8
@@ -223,6 +223,14 @@ a file checked into the repository which is a template or set of defaults which
223 can then be copied alongside and modified as appropriate. This second, modified
224 file is usually ignored to prevent accidentally committing it.
225
226 +[[fetching-and-pulling]]
227 +How do I know if I want to do a fetch or a pull?::
228 + A fetch stores a copy of the latest changes from the remote
229 + repository, without modifying the working tree or current branch.
230 + You can then at your leisure inspect, merge, rebase on top of, or
231 + ignore the upstream changes. A pull consists of a fetch followed
232 + immediately by either a merge or rebase. See linkgit:git-pull[1].
233 +
234 Hooks
235 -----
236