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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

Missing commits in branches


I saw yesterday that there was an outage with some BitBucket services. 

This seems to have affected some repos of mine, in terms of branches and commits.

I can see the branches in BitBucket, but I cannot see the commits in the branches.

A `git log` locally on the branches shows that code was committed to these branches, but BitBucket is not showing them.

I have a branch that other branches have been merged into (a release candidate), but because BitBucket is missing the commits to the merged in branches, I cannot merge this into master as BitBucket seems to the think that the release candidate and master have no changes


Any help will be great!

1 answer

0 votes

Hi @craigwillis-a12

I was about to create a support ticket for you to allow us troubleshooting your repository, but I noticed you already did that. Let's follow the investigation with our support team and if the fix can bring benefits to other users we can share our findings here.

Thank you for opening the support ticket. The community channel is limited to issues that can be publicly investigated.

has the issue got resolved ? if yes, how ?

We are facing the same issue now !

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events