git pull --rebase lost commits after coworker's git push --force

Question

I thought I understood how git pull --rebase was working, but this example is confusing me. I would have guessed that the following two scenarios would produce identical res

Answer 1

Yeah, this looks right. Brian's git push --force is going to set the latest commit as the one he has on his local system. If Brian had first pulled any latest commits and then git push --force the results would be the same.

Here is a good thread with more info: Force "git push" to overwrite remote files