Incorrect commit order in commits tab
in progress
L
Lime Beetle
Commits tabs breaks topology rules, when displaying history that contains merge commits.
See screenshots for examples (https://github.com/torvalds/linux)
In this example the first displayed commit in gitness is 85a71e, which is a grandparent of 3913335 and parent of c48617. I.e. it appears at least two commit earlier than it should.
Log In
P
Patrick Wolf
in progress
This was identified as a bug and will be fixed soon
P
Patrick Wolf
under review
Hi, Lime Beetle
I'm cloning Linux to my project to replicate these issues. I might have some questions after I get it copied over