You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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.
Problem
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...
https://stackoverflow.com/questions/61002882/bitbucket-not-showing-recent-commits-but-commits-are-still-present
Hi, @mbm!
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.
Kind regards,
Caroline
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, @mbm! I'm glad to help :)
Kind regards,
Caroline
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Well this had me somewhat worried and doubting everything I knew and ever did -
But the empty commit fixed it - thanks for sharing, and saving me a lot of new, grey hair ;)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.