The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Source tree not showing merge line in history

Matthew Cawley
Contributor
July 4, 2019

From some pull requests, the merge line is not visible.

What is the cause of this as it leads to misinterpretation of branch state?

Thanks :)

Screenshot 2019-07-04 at 12.53.53.png

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Mike Corsaro
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 8, 2019

Hello! That's odd -- if you click on the merge commit is one of the parent commits listed the commit below it? It would help if I knew the SHA of both parents and the SHA of both commits.

 

Thanks!

Matthew Cawley
Contributor
October 21, 2020

Sorry for the delayed response :D - I forgot I asked the question.

The issue still exists as you can see from the attached screenshot

Screenshot 2020-10-21 at 19.53.35.png

The merge was done using a Pull Request via Bit Bucket.

If I click on the master branch, the commit history doesn't seem to exist, it appears to have squashed it down (default setting from BitBucket)

The 'parents' information is the previous merge onto the master branch.

I'm guessing the issue may be a result of a squashed merged, if it is, is there not a better way of representing this in the UI so it is clear that branch has been closed?

Like # people like this
TAGS
AUG Leaders

Atlassian Community Events