' Risky' in a way that git pull will merge even those changes that are not required or those which you do not want to merge. It might sound risky, but in the industry, git pull gets used very commonly. The user is just notified about the result of the command, whether the operation was successful or failed, including any warnings, etc. Hard to digest? Let's see a bit more.Įxecuting a git pull command will merge the changes without notifying the user or displaying what changes are merging. Git Pull will perform Git Fetch without telling the user and merge those changes automatically without asking from the user. Here's the magic that I was talking about at the start. If you think that fetching is all that Git Pull does, then why aren't we satisfied by Git Fetch? In a way, ' fetch' is not the right word because we already discussed git fetch command. ' Pull', which is self-explanatory, depicts that the user is trying to fetch something from the repository. Git pull is a magical way to perform a combined operation of git-fetch & git-merge with a single command. What different options are available In Git Pull?.Git fetch and Git merge commands are so commonly used that Git has a special command that combines both of these commands into one command called Git Pull command. Is there something that can combine both of these processes? Yes, there sure is. The problem is that if the user is using Git fetch ten times in a day and all of the changes have to merge, the git merge also gets used ten times. Git fetch, and Git merge are used together for merging the changes and accepting them. Both of being highly prevalent in Git, they are used very frequently.

In the last tutorial, we got familiar with the Git fetch and Git merge command.

Git bash tutorial clone pull push