Pushed GIT commit not shown in bitbucket repo

I just did some experimentation in my local git repo, checking out an old commit for inspection, then checking out the top level and re-setting the head to it.

I then made one commit and pushed it to bitbucket. The origin bitbucket URL is correct and git push -v indicates that all is well:

= [up to date] master -> master

updating local tracking ref 'refs/remotes/origin/master'

Everything up-to-date

But the commit does not appear in my bitbucket list of commits. Is it common for there to be a time lag between push and display of commits? (or should I be worried?)

1 answer

1 accepted

Turns out it was a Git newbie error; I had inadvertently created a new branch. This morning after some sleep I merged the branch back into master, pushed to bitbucket and the new commits appeared immediately.

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda&nbsp...

2,048 views 1 5
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you