Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,558,901
Community Members
 
Community Events
184
Community Groups

Bitbucket commits view loses commit history

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

1 answer

1 vote
Caroline R
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 16, 2021

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

Wow, that was really precise and helpful, thank you Caroline!

Like Raoul likes this
Caroline R
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 21, 2021

Hi, @mbm! I'm glad to help :) 

Kind regards,
Caroline 

Like Raoul likes this

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 ;)

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events