Is anyone else having incorrect commit histories when pulling?

[Thomas Johnson]

Hey y'all,

In Bitbucket, I can clearly see a commit I pushed 47 minutes ago. I went to my other machine and did a successful "Up to date" git pull, and I do not see it.

Is Atlassian having server issues again?

Bitbucket UI

GitHub Desktop - Repository History

I hopped back on the other computer and no matter how many times I click "Push origin", it doesn't.

The last time I experienced this kind of issue, there was an outage.

The Bitbucket status page says all systems operational which is clearly not true.

Thanks in advance,

-T

[Thomas Johnson · Accepted solution]

The answer is to move your stuff to GitHub because this is the second time this has happened without any kind of status update from Atlassian. Peace out.

[Erez Maadani]

Hey @Thomas Johnson 

Try pulling your code using the git cli.

If if it manage to pull all history, it's a client issue.

If it doesn't and there are no connection issues, it could be BitBucket side or some machine between the client and BitBucket.

If there are connection issues, they have to be solved first ;)  

[Thomas Johnson]

I have done that. git cli is returning with "Everything up-to-date" on push and "Already up to date." on pull.

This is a Bitbucket issue.