Gerrit merges create branches without parent nodes

[veremenko-y]

Do you want to request a feature or report a bug?
bug/feature

What is the current behavior?

After moving to gerrit, it creates merge commits from /refs/for/* branches, and this results in merges with no parents. I understand why it happens, but after some time it will bloat the whole repository with those hanging branches.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.

What is the expected behavior?

Maybe do not display them, or display the dotted branch and do not extend it to the beginning of the history

Environment you encounter the issue:

• GitExtensions version: 2.50.01
• GIT version: git version 2.13.2.windows.1
• OS version: Microsoft Windows NT 10.0.15063.0

Did this work in previous version of GitExtensions (which)?
N/A

[chillitom]

Also seeing this. At first I was worried merge history was being incorrectly recorded but after checking git log I can see it is all there.

Take something like the following:

* b50eb80
*   8a9afaf
|\
| * 27c4982 
* | 9508381 
* | 75dd942 
* | 8789bd8 
|/
* 9c62d31 
* 77cbc02

This is being displayed as a tree equivalent to this:

* b50eb80
*   8a9afaf
|\
* | 9508381 
* | 75dd942 
* | 8789bd8 
* | 9c62d31 
* | 77cbc02

From Git Extensions the only visible evidence of the work performed in commit 27c4982 is in the merge commit 8a9afaf.