When you are getting confuse in git pull and git fetch, here is the some solutions, may be helpful.
In the simplest terms,
You can do a
A
or
In the simplest terms,
git pull does a git fetch followed by a git merge.You can do a
git fetch at any time to update your remote-tracking branches under refs/remotes/<remote>/. This operation never changes any of your own local branches under refs/heads, and is safe to do without changing your working copy. I have even heard of people running git fetch periodically in a cron job in the background (although I wouldn't recommend doing this).A
git pull is what you would do to bring a local branch up-to-date with its remote version, while also updating your other remote-tracking branches.or
- When you use pull, Git tries to automatically do your work for you. It is context sensitive, so Git will merge any pulled commits into the branch you are currently working in.
pullautomatically merges the commits without letting you review them first. If you don’t closely manage your branches you may run into frequent conflicts. - When you fetch, Git gathers any commits from the target branch that do not exist in your current branch and stores them in your local repository. However, it does not merge them with your current branch. This is particularly useful if you need to keep your repository up to date, but are working on something that might break if you update your files. To integrate the commits into your master branch, you use merge.
Posts
