Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Bitbucket creates branch like it is created by different person Edited


This morning I wanted to create a branch for my task. I created the branch but after I realized the branch looks like it is created by someone else in my team. I deleted the branch and created again, and it had another person's name on it. I realize that the branch is created by the name of the last person who merged code to Develop branch. This never happened before. Also, the branch's creation date is the same as the merge time. This causes some issues about filtering, adding reviewers to the PR and so on. Do we know about some kind of behavior as normal or is this a bug that needs to be solved?

Best Regards,


1 answer

0 votes

Hello @Idil_Baykent ,

Welcome to the Community!

A branch in Git is just a pointer to a commit. It has no metadata other than the name and commit hash, that is there's no creator or creation date for a branch. Commit also doesn't reference any branch (unlike Mercurial), the pointer is one-way.

I guess by "branch looks like it is created by someone else" you mean the Updated column in the branch list view? It shows the metadata of the commit that branch points to, so yes, what you observed is the expected behaviour. As soon as you make any commit on that new branch, it'll show the metadata of your commit instead: when you push a commit, the pointer of the relevant branch is moved to the new tip commit.

Does this make sense? Let me know if you have any questions.


Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bitbucket

Calling any interview participants for Bitbucket Data Center

Hi everyone,  We are looking to learn more about development teams’ workflows and pain points, especially around DevOps, integrations, administration, scale, security, and the related challeng...

485 views 5 4
Read article

Community Events

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

Events near you