The although the answer is quite thorough in almost every example you had to be doing something else incorrectly for git pull to be an issue.

I have often railed with other developers working on mid/large sized projects about having this pristine git history where commits are all tailed back to back. My main issue with this is the fact that you never get a commit for when two branches come together so you never really know when an issue was introduced.

i.e.

Branch A works. Branch B work.

Branch A-B doesn't work. No merge commit to show introduction of bug.

People in general practice should not be force pushing.

Most of the arguments seem to be against not know what you are going to get which can be preempted with a fetch portion of git pull, but if you don't trust people you are working with, work with new people.

git pull doesn't delete old branch just as git add doesn't to delete old branches, I am not even sure making an argument like that means, its not what git pull is for.