Why Commit Logs Disappear from Git's Local Repository

I manage the source using Git.
The phenomenon of "When I pull, all commits that I hadn't pushed disappeared" occurred in the environment of several people.
Even the commit log of "commit I didn't push" seems to have disappeared from their local repository.

What can you think of as the cause of this kind of situation?
For Git clients, SourceTree (Windows version) is used.

[Additional note]
I also multi-posted teratail.
https://teratail.com/questions/49918

git

2022-09-30 18:30

1 Answers

I don't use SourceTree, so I don't know the actual display, but

$git pull -- rebase instead of merge when rebase#pulling

creates conflicts and all conflicts

$git rebase --skip#Skip without applying conflicting commits

I have confirmed that the local commit will be dangling (which appears to have disappeared).

Did you do this by mistake?

2022-09-30 18:30

If you have any answers or tips

Popular Tags

python x 4647

android x 1593

java x 1494

javascript x 1427

c x 927

c++ x 878

ruby-on-rails x 696

php x 692

python3 x 685

html x 656