Push: delivers commits to the recipient and requests that they update their branch. This necessitates that everything on their end is in order. It is impossible to combine simultaneous growth in this way. Pull: executes git fetch, which fetches commits and updates your Git's remote-tracking name, before running a second Git command to update your branch.
The git fetch command copies commits, files, and references from a remote repository to your local repository. Fetching is what you do when you want to know what other people have been up to.
The git push command is used to transfer content from a local repository to a remote repository. Pushing is the process of sending commits from a local repository to a remote repository. It's similar to git fetch, except that instead of importing commits to local branches, pushing exports them to remote branches.
git pull origin/master merges changes from the locally stored branch origin/master with the checked-out branch. The origin/master branch is a "cached copy" of what was last fetched from origin, which is why it's referred to as a remote branch in git.
It's no secret that using git push —force is risky. It will, without a doubt, replace the remote with your local changes—and it will not check to see if this will override any changes made up to the remote throughout the process. Even the most cautious development team faces danger while working in a shared repository.
