The 4 new commits on dev are the 4 red dots closest to the top, before the green fork. The green "branch" are the commits on master. The #4057 commit should be connected to the #4108 commit instead of the #4125 commit.
The parent & child detail links on individual commits look correct to me
It's not clear to me what branch and/or starting point the commit browser uses (dev? master? last commit?). Perhaps that could be clarified. It's possible that that it's a problem in the browser and the commit runs are correct.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
To ssh://engr.geek.net/forge
+ c1219ac...0017534 tv/3759 -> tv/3759 (forced update)
Commit run data was fine. There was a bug in the topological sort of commits that was causing the commit graph to render incorrectly. Fixed that and added a test. Also did a visual comparison of the graph to:
git log --graph --pretty=oneline --abbrev-commit dev
and found that they matched. There are some minor differences in the rendering, but the branches are consistent.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Commit runs aren't displayed correctly in the commit browser
It's not clear to me what branch and/or starting point the commit browser uses (dev? master? last commit?). Perhaps that could be clarified. It's possible that that it's a problem in the browser and the commit runs are correct.
To ssh://engr.geek.net/forge
+ c1219ac...0017534 tv/3759 -> tv/3759 (forced update)
Commit run data was fine. There was a bug in the topological sort of commits that was causing the commit graph to render incorrectly. Fixed that and added a test. Also did a visual comparison of the graph to:
and found that they matched. There are some minor differences in the rendering, but the branches are consistent.
Not merging - [#4142] will be responsible for that.
Related
Tickets:
#4142