Under some scenarios, Bitbucket stops displaying commits for a branch, even though the repository itself is fine.
Loads of people "fixing" it by re-pushing their commits and branches. Would be nice to find this needle in the haystack and remove it.
This has been around a while and perhaps not understood well. The Atlassian comment about it being caused by a forced push ignores the underlying bug.
You are not seeing previously available commits in your repository. These missing commits are usually a result of a force push that has rewritten history in the Git repository.
Here's more user feedback... 4k views and counting...
Thank you for reaching out to Atlassian Community!
It looks like you're affected by a bug. This bug can occur intermittently, and our team is already looking into addressing it:
As you have mentioned, as a workaround (while this problem is not fixed), you can push another commit or a new branch to the repository.
Our development team will post an update on the bug report when this is fixed. If you are not familiar with our Bug Request Policy, you can read more about it here.
You can add yourself as a watcher (by selecting the Start watching this issue link in the bug report) if you'd like to get notified via email on any updates and also select the This affects my team link to indicate you are affected by this issue.
Please, feel free to share any additional questions or concerns regarding this case.
Hey Community! We’re willing to wager that quite a few of you not only use Bitbucket, but administer it too. Our team is excited to share that we’ll be releasing improvements throughout this month of...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events