Despite the merge, the develop branch displays as N commits behind the master branch.

[Ali Raza]

I have merged my master branch into develop via a PR, that PR is merged with Squash strategy but develop branch still shows me that it is N commit behind master on branches page. 

[Theodora Boudale]

Hi Ali,

This is expected behavior if you merge with the squash strategy.

The behind count shows you the number of commits that exist on the main branch that are not reachable from the head of the branch you're looking at (develop).

When you merge with Squash, you merge the changes into develop, but the commits you squashed from master still exist on master and they are not reachable by develop. (edited because the info I provided earlier was incorrect)

This works similarly with git log.

We have a feature request for changing this behavior: https://jira.atlassian.com/browse/BCLOUD-19572 The feature request has been closed because it is unlikely to be worked on in the near future. However, you can still add a comment to express your interest, as our product managers continue to monitor closed requests as well.

Kind regards,
Theodora