'New commit won't `git pull` but `git reset` works
I don't know how this happened but a change was pushed to Gitlab, the new commit is at the top of the commit history in Gitlab, but if you git pull you don't get it. Even a fresh git clone gives you the second most recent commit. Running git log -1 doesn't show the new commit. The only thing I've found that works is to copy the SHA from Gitlab and git reset to that SHA.
What is up with this ghost commit that's visible in Gitlab but unreachable from the CLI unless you know its secret SHA?
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|